When a DSA receives a request that uses the simple-paged results or virtual list view control, the DSA compares the page size used in the request with the page size specified in the set paging-threshold command.
The DSA uses the relative sizes of the page size in the request and the paging threshold to decide how to handle the request.
If the page size in the request is greater than the paging threshold, the DSA sorts the results and then returns the first page to the client.
If the page size in the request is less than the paging threshold, the DSA can collect the page “on the fly”. If this happens, the entire result is not sorted.
By default, the paging threshold is 100 entries. If you want to change this threshold, use the command set paging-threshold.
Example: How a DSA handles a request with paging and sorting
A client sends a request to the DSA, asking for all users whose surname begins with ‘A’. In this example, there are 120 such users.
The client asks that the results be paged, with only 20 results included in each page. This means that the DSA sends the first 20 results, and then the next 20 results, and so on until it has sent all of the results.
However, in this example, the client wants the request to be both paged and sorted.
The page size of 20 is smaller than the paging threshold (by default this is 100). This means that the DSA sorts the entire list of all surnames beginning with ‘A’, and it returns the first 20 entries to the client.
|
Copyright © 2013 CA.
All rights reserved.
|
|