Changes for page 1. SearchHotelPrices

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -402,57 +402,7 @@
402	402	{{/code}}
403	403
404	404
405		-**Overview:** The Paging and Caching mechanism is designed to efficiently manage data retrieval in a paginated format. This mechanism is essential for handling large datasets by dividing the data into manageable pages, thereby optimizing the performance and scalability of data retrieval operations.
406	406
407		-**Initial Request:**
408		-
409		-* **Purpose**: The first request initiates the paging process and is designed to fetch the initial set of data without utilizing a pagingId.
410		-* **Parameters**:
411		-** pagingId: Should be set to an empty string ("") to indicate that this is the initial request.
412		-** pageNumber: Indicates the specific page of data to retrieve, starting with 1.
413		-** pageRowCount: Specifies the number of results to be included on each page.
414		-
415		-**Example - First Request**:
416		-
417		-{{{{
418		- "pagingId": "",
419		-  "pageNumber": 1,
420		-  "pageRowCount": 10
421		-}
422		-}}}
423		-
424		-
425		-**Subsequent Requests with Caching:**
426		-
427		-* **Purpose**: Following the initial data retrieval, subsequent requests utilize the pagingId obtained from the previous response. This pagingId serves as a cache identifier, enabling the system to quickly access the relevant dataset and efficiently paginate through the data.
428		-* **Cache Utilization**:
429		-** Upon receiving a response, a pagingId value is provided. This pagingId should be used in subsequent requests to reference the cached data.
430		-** To navigate through the dataset, adjust the pageNumber while keeping the pagingId constant.
431		-** To refresh the dataset and clear the cache, initiate a new request without a pagingId.
432		-
433		-
434		-**Example - Request with Caching**:
435		-
436		-{{{ {
437		- "pagingId": "80",
438		- "pageNumber": 2, // Adjusted to fetch the next page
439		- "pageRowCount": 10
440		- }
441		-}}}
442		-
443		-
444		-**Cache Management:**
445		-
446		-* Clearing the cache and fetching a fresh set of data requires sending a new request with the pagingId parameter omitted or set to an empty string. This action resets the pagination and caching context.
447		-
448		-**Implementation Notes**:
449		-
450		-* The paging and caching mechanism significantly enhances data retrieval efficiency by minimizing server load and optimizing response times.
451		-* Developers should ensure that the pagingId is correctly managed between requests to maintain session continuity and data consistency.
452		-
453		-This documentation outlines the procedural framework for implementing a robust paging and caching strategy within data retrieval systems, detailing parameter usage and operational best practices for both initial and subsequent data fetch operations.
454		-
455		-
456	456	== Important ==
457	457
458	458	{{error}}