> As Rob indicates, one possibility is the 1.1 resultSetTTL value which
> the client can use to indicate how long the result set should hang
> around. I can't remember all the discussion on this, but perhaps a
> resultSetTTL of 0 could be used to explicitly terminate the result set.
I think that was what was decided, as the TTL says 'don't keep me around
at all' so if used with an existing result set it would effectively delete
> Of course, for this to work in the general federated case, you probably
> want all the SRW servers you are searching to have the same behaviour.
> This is probably best done as a federated SRW profile than part of the
> core SRW spec (others may differ on this point).
It's still a business model. My server won't care either way about
authentication token delimited sessions when searched in a federated
environment (I still don't understand this new use of 'federated')
I think a collection of business model supporting recommended best
practices, or just plain discussion papers would be useful, but isn't
necessarily for us to write. I'd be happy to take part in a discussion on
such things, and that the LoC site might host them, but I don't think it
should be something which is part of SRW proper. We certainly can't
mandate the support for various business models to implementers.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Nebmedes: telnet: nebmedes.o-r-g.org 7777
____/:::::::::::::. WWW: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I