Skip to content

Commit 1615278

Browse files
authored
server-side pagination reasoning
1 parent 388b4ce commit 1615278

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

graph/articles/collections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -217,7 +217,7 @@ RESTful APIs that return collections MAY return partial sets.
217217
Consumers of these services MUST expect partial result sets and correctly page through to retrieve an entire set.
218218

219219
There are two forms of pagination that MAY be supported by RESTful APIs.
220-
Server-driven paging mitigates against denial-of-service attacks by forcibly paginating a request over multiple response payloads.
220+
Server-driven paging allows servers to even out load across clients and mitigates against denial-of-service attacks by forcibly paginating a request over multiple response payloads.
221221
Client-driven paging enables clients to request only the number of resources that it can use at a given time.
222222

223223
Sorting and Filtering parameters MUST be consistent across pages, because both client- and server-side paging is fully compatible with both filtering and sorting.

0 commit comments

Comments
 (0)