> These TTLs are just hints, not promises. If the result set TTL says 100
> seconds of idleness and the session goes with 50 seconds of idleness, then I
> guarantee that the result set will go away with the session.
> What's the problem?
There isn't a /problem/ just that your promise of no result set after
session and another implementation's views on the matter could be
(For example my example of resultsets after session expiration becoming
'public property', so to speak)
Does this need to be set down in the protocol or not then?
I think both approaches are perfectly valid.
,'/:. 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