LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  June 2002

ZNG June 2002

Subject:

Re: Betr.: SessionID Summary

From:

Ray denenberg <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Wed, 19 Jun 2002 10:13:41 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (18 lines)

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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager