Description
This means that:
- The results should have a natural ordering, like timestamp or sequence number for Audittrails. Oldest entries should be listed first.
- The request must be able to define a 'From' date or sequence number.
- The request should be able to define a MaxNumberof results.
Note that all 3 result sets already contains timestamp which can be used to order the results. Even better, for AuditTrails we have sequence numbers.
This means that we need to add:
- A 'MaxNumberOfResults' to all 3 request types.
- A from element to the getFileIDs and getChecksums requests.
- We might also chose to implement the FileID pattern from the AuditTrails, replacing the current 'FileIDs' element.
Attachments
Issue Links
- is depended by
-
BITMAG-745 SB Pillars should support paging for GetAuditTrails, GetChecksums and get FileIDs
- Resolved
-
BITMAG-746 Reference pillars should support paging for GetAuditTrails, GetChecksums and get FileIDs
- Resolved
-
BITMAG-747 KB Pillars should support paging for GetAuditTrails, GetChecksums and get FileIDs
- Resolved
-
BITMAG-748 Reference clients should support paging for GetAuditTrails, GetChecksums and get FileIDs
- Resolved
- related to
-
BITMAG-764 Implement workflow for request newer checksums and fileIDs
- Resolved