Subject: What happens if client sends request again and again?
Author: SteveHB
In response to: What happens if pageSize < sizeLimit ?
Posted on: 01/23/2012 01:08:36 PM
A client may have any number of outstanding search requests pending,
any of which may have used the pagedResultsControl. A server
implementation which requires a limit on the number of outstanding
paged search requests from a given client MAY either return
unwillingToPerform when the client attempts to create a new paged
search request, or age out an older result set. If the server
implementation ages out an older paged search request, it SHOULD
return "unwilling to perform" if the client attempts to resume the
paged search that was aged out.
In order to serve the PagedResultsControl, the serve may have to prepare and hold the whole result set on the server side for each client associated a cookie. If a client open too many requests and leave them open without consuming the results, this will be a burden on server and might choke the server. In that sense, the server can defense itself by aged out the previous requests for the specific client.
>
> On 03/11/2008 06:59:49 PM
SteveHB wrote:
'sizeLimit' will be ignored by nature.
Search Paged Results Control is per operation rather than connection. When you associate the Search Paged Results Control with a search, you expect the number of results returned is governed by 'pageSize' -- the 'sizeLimit' is therefore useless for this search.
References:
