The client asks for a specific page number, the server returns that page's items and info, and the client can request more pages until done.
Execution Sample
Rest API
GET /items?page=1&size=3
Server returns items 1-3
GET /items?page=2&size=3
Server returns items 4-6
Shows how client requests pages with size 3 and server returns corresponding items.
Execution Table
Step
Request URL
Page Number
Page Size
Items Returned
Next Page Available
1
/items?page=1&size=3
1
3
[Item1, Item2, Item3]
Yes
2
/items?page=2&size=3
2
3
[Item4, Item5, Item6]
Yes
3
/items?page=3&size=3
3
3
[Item7, Item8]
No
4
/items?page=4&size=3
4
3
[]
No
💡 Step 4 returns empty list because no more items exist after page 3
Variable Tracker
Variable
Start
After Step 1
After Step 2
After Step 3
After Step 4
page
undefined
1
2
3
4
size
undefined
3
3
3
3
items_returned
[]
[Item1, Item2, Item3]
[Item4, Item5, Item6]
[Item7, Item8]
[]
next_page_available
false
true
true
false
false
Key Moments - 3 Insights
Why does the server return an empty list at step 4 instead of an error?
Because the requested page number 4 has no items left, the server returns an empty list to show no data, not an error. See execution_table row 4.
How does the client know if there is a next page?
The server includes metadata like 'Next Page Available' which is true if more items exist. See execution_table column 'Next Page Available'.
What happens if the client requests page 0 or a negative page?
Usually the server treats invalid page numbers as page 1 or returns an error. This example assumes valid positive pages only.
Visual Quiz - 3 Questions
Test your understanding
Look at the execution_table, what items are returned at step 2?
A[Item1, Item2, Item3]
B[Item7, Item8]
C[Item4, Item5, Item6]
D[]
💡 Hint
Check the 'Items Returned' column at step 2 in the execution_table.
At which step does the server indicate no next page is available?
AStep 3
BStep 2
CStep 1
DStep 4
💡 Hint
Look at the 'Next Page Available' column in the execution_table.
If the page size changed to 2, how would the items returned at step 1 change?
A[Item1, Item2, Item3]
B[Item1, Item2]
C[Item1]
D[]
💡 Hint
Page size controls how many items are returned per page, see variable_tracker for 'size'.
Concept Snapshot
Page-based pagination lets clients request data in pages.
Client sends page number and size.
Server returns that page's items plus info if more pages exist.
Client repeats requests for next pages until no more data.
Helps load data in small chunks for better performance.
Full Transcript
Page-based pagination is a way to get data from a server in small parts called pages. The client asks for a specific page number and how many items per page it wants. The server then sends back just those items for that page. It also tells the client if there are more pages to get. The client can keep asking for the next page until the server says there are no more items. This method helps avoid loading too much data at once and keeps the app fast and responsive.