Currently, the server solely decides whether or not to apply server-driven paging on the result set, and clients are expected to handle next-links returned as part of a partial result. Methods should be introduced to allow clients to adapt this paging mode to their needs.

First, if clients could indicate their preference to apply server-driven paging for fetching the result, then the server would have more knowledge about potential subsequent client interactions. The server could leverage it by preparing a result set that remains stable over the different page accesses. This cannot be achieved by client-side paging in any way.

Second, the client is currently expected to handle next-links as they occur, but cannot control the page size. A preference to specify the maximum number of entries returned in a server page would allow clients to consider boundary conditions of their runtime infrastructure.