> > > I would say, that it is preferred that resultsets time out later than
> > > sessions but when it is the other way around, the client could save the
> > > original CQL to re-execute the query.
> > The seems very strange to me. Surely the implication of having a result
> > set last longer than the session is that result sets can be accessed out
> > side of a session?
> Interesting philosophical question but is there any reason why the protocol
> needs to address it? It seems to me that the protocol can be silent on this.
Yup. An implementation can keep sessions around for as long as they want,
even after the session TTL. Perhaps after the session expires they get
turned into 'this is what people have been searching for' information or
similar and make them open access in the remaining TTL.
,'/:. 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