Changes between Version 1 and Version 2 of Ticket #50244, comment 25
- Timestamp:
- 07/07/2020 11:01:31 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #50244, comment 25
v1 v2 11 11 What you're saying, as I understand, is that there is value in having two modes of operating: 1. Pre-validation as described above when the route supports it 2. Simple batch processing for all routes - e.g. sending over 100 requests and expecting that e.g. 60 of them would succeed while 40 would fail. Can you think of some specific use cases where that would be handy? Also, we'd need to distinguish between: 12 12 13 1. Batch requests with pre-validation vs no pre-validation (different URL? request parameter ?)13 1. Batch requests with pre-validation vs no pre-validation (different URL? request parameter as discussed earlier?) 14 14 1. Endpoints supporting pre-validation vs endpoints not supporting pre-validation (route config?)
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)