Robert Sanderson wrote:
> I assume that the server is able to set a low session TTL for the first
> response and then increase it later if it gets back another request with
> that sessionid.
More basically, I assume the server can update the ttl on subsequent responses.
It could continually set it to 1 minute, for example. Or, it could set it to 10
minutes and then if the subsequent request is 3 minutes later, set it to 7
minutes. I assume that it can't (or that it would be perceived unfriendly if it
were to) unduly decrease it, for example set it to 10 minutes and 3 minutes later
set it to 1 minute. However, I don't suppose any of this needs to be articulated
(other than in some "best-practices" document).
So please look at http://www.loc.gov/z3950/agency/zing/service.html and see if
this about captures what we want to say.