Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 25.1
edited by Giorgi Mdivnishvili
on 2024/04/10 11:12
Change comment: There is no comment for this version
To version 28.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -864,6 +864,8 @@
864 864  |totalCount|integer|The total count of packages.
865 865  |error|boolean|Indicates whether there was an error.
866 866  
867 +=== ===
868 +
867 867  === Paging and Caching ===
868 868  
869 869  During the first request, Paging id must be  empty like this  ( "pagingId": "",)  pagenumber is the number of the page, pagerowcount means number of the given result in one page. So in the first request we can search like this:
... ... @@ -879,10 +879,12 @@
879 879   }
880 880  {{/code}}
881 881  
884 +While making first search request, paging id should be empty,  "pageNumber":  and  "pageRowCount":10 means that, in response there will be returned maximum 10 packages per page.
882 882  
886 +
883 883  ==== Request with caching ====
884 884  
885 -as we receive response, in the end we can see pagingId- number, chich we can use for caching, and then just switch pagenumbers. for cleaning cache, it's important to make new request without pagingID
889 +after receiving response from first search request, in the end we can see pagingId- number, wchich we can use for caching, and (pageinatoin) for switch pagenumbers, and displaying results as we whant. For cleaning cache, it's important to make new request without cllear pagingID, like this  "pagingId": "",
886 886  
887 887  {{code language="Json"}}
888 888   {