Server-side sorting is intended for use by clients that are unable or unwilling to sort results themselves; this might be useful in hand-held clients with limited memory and CPU mojo.
The advantages of server-side sorting include, but not limited to:
- the server can enforce a time limit on the processing of the sorting
- clients can specify an ordering rule for the server to use
- professional-quality servers can be configured to reject requests with sort controls attached if the client connection is not secure
- the server can enforce resource limits, for example, the aforementioned time limit, or administration limits
- the server can enforce access restrictions on the attributes and on the sort request control itself; this may not be that effective if the client can retrieve the attributes anyway
- the server may indicate it is too busy to perform the sort or simply unwilling to perform the sort
- professional-quality servers can be configured to reject search requests for all clients except for clients with the necessary mojo (privilege, bind DN, IP address, or whatever)
The disadvantages include, but not limited to:
- servers can be overwhelmed by sorting large result sets from multiple clients if the server software is unable to cap the number of sorts to process simultaneously
- client-side APIs have to support the server-side sort request control and response
- it might be easier to configure clients to sort by their own ‘ordering rules’; although these can be added to professional-quality, extensible servers
1
solved LDAP Server side sorting – really a good idea?