Summary of proposal to allow clients to request result sets.
Servers need to know the intention of the client with respect to a search.
If the client wishes to reuse the results, then a result set should be
created. If the client is happy to reissue the search, or does not expect
to reuse the result set then the server does not have to create a result
set. However there is no way in version 1.0 for the client to send this
information to the server.
A new optional parameter on the request is proposed, <resultSetTTL> with
type of 'integer', and qualified to be nonNegative. If this parameter is
0, then a result set is not required and this is the default if not
supplied. If the result set is positive, this is the number of seconds
that the client would like the result set to be kept alive for.
It is not necessary to obey this request.
If a server does not support result sets, then it may still return the
matched records with a non-fatal diagnostic that result sets are not
supported, or fail the request entirely.
If the TTL requested is not supported, then it may either fail the request
entirely or return the result set with the actual TTL. For example, if
the requested time is 86400 (1 day) then the server may still create a
result set with a TTL of 10 minutes.
There are no known compatability issues.
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Twin Cathedrals: telnet: liverpool.o-r-g.org 7777
____/:::::::::::::. WWW: http://liverpool.o-r-g.org:8000/
I L L U M I N A T I