Hi @tomas-thin-gale,
The Query API seems to use a mandatory pageNumber and pageSize whereas the current LIST_DOCUMENTS rpc uses a pageSpec with limit and offset.
A12-15813 talks about a rough integration of Infinite Scrolling for the Overview Engine but I couldn’t find any further details. I imagine all the hard work is done by the Overview Engine and Data Services but from a modeling / end-user perspective, I have the following questions:
- Will the end-user notice any difference between the current implementation and Query API version of Infinite scrolling?
- Pagination is currently recommended for performance reasons, will this recommendation remain with the Query API?
Hi @malcolm-silver-ice,
The pagination based on full size, limit and offset is equivalent to full size, page number and page size pagination. One can be turned into the other with simple translation logic. Full size is the same in both cases, limit is equal to page size and number of pages available can be calculated by following formula: Full size % page size (+1 if there is remainder in division). Therefore, there should be no difference in the infinite scrolls or in any other pagination aspect in UI.
Pagination is a good practice. Every selection request in DS will be paged. Customer projects can set very high page numbers to page as little as possible, but this opens doors to DoS attacks. DS & SP do not recommend this approach.