> Date: Tue, 18 Jun 2002 11:29:58 -0400
> From: "LeVan,Ralph" <[log in to unmask]>
>
> So, the client bids for a sessionID in a request and gets one
> (probably with a TTL (Time To Live) value like resultSetID's).

Yes. But it would be helpful if, along with the "bid", the client can
include a suggested TTL value which polite servers will try to
honour.

The same goes double with result set TTLs, since only the client can
have any idea how long it's likely to need the set. For example, a
Zthes client will typically fire of dozens of little searches as it
navigates around the semantic hierarchy, and should be able to clue
the server in that it doesn't need to keep the result sets around for
posterity. But the same client might also search for the "thesaurus
front matter" record, and want that result set to be kept around for
much longer -- for the life of the session, in fact.

 _/|_ _______________________________________________________________
/o ) \/ Mike Taylor <[log in to unmask]> www.miketaylor.org.uk
)_v__/\ "Owen and Fowler whacking them in at one end, Babb running
         into goalposts at the other" -- Matt Clark's summary of the
         Evans era.