Client-side paging retrieves the complete result set, then lets the client divide it into pages that users browse one page at a time. It suits an endpoint that already returns all board games, but large unordered responses can be difficult for clients to use. section 5.4 section 5.4.1
A client-side paging design involves these responsibilities:
- The web API returns the complete data set in one response. section 5.4.1
- The client creates the multipage interface and displays a limited number of results in each view. section 5.4.1
- The client can browse pages without requesting each displayed subset separately from the server. section 5.4.1
Board-game results
A GET request to /BoardGames returns a large JSON list. The client consumes that complete list and builds a multipage board-game view, showing only a limited number of records at a time. section 5.4 section 5.4.1
Use the long board-game list to see why a client may need to split a complete response into discrete pages. section 5.4
