Date:         Wed, 19 Jun 2002 10:13:41 -0400
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         Ray denenberg <[log in to unmask]>
Subject:      Re: Betr.: SessionID Summary
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Content-Type: text/plain; charset="iso-8859-1"

From: "Robert Sanderson" <[log in to unmask]>
> > 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?
>
> But if you're going to have sessions and I assume limit access to
> resultsets to only those created during that session, what is the point of
> having them last longer than the 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.

--Ray