I'm not talking about keeping state. The numberOfRecords is returned in
each response. I just want to say that when you return for example:
<srw:numberOfRecords>approximately 123</srw:numberOfRecords> or
there doesn't seem to be a reason to return a diagnostic or to introduce
an extension that says that you don't mind about the numberOfRecords.
Van: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]]
Namens Roger Wallin
Verzonden: donderdag 9 augustus 2007 12:02
Aan: [log in to unmask]
Onderwerp: Re: numberOfRecords
On Thu, 9 Aug 2007 10:41:12 +0200, Theo van Veen wrote:
>The numberOfRecords is used for 2 purposes:
>1) presentation for the user
>2) to let the client check if browsing to the next records makes sense
>Wouldn't it be much simpler to use the contents of numberOfRecords to
>indicate that there the number or exact number is unknown rather than
>introducing a new extension and diagnostic?
>It seems overkill to me to introduce an extension to let the client say
>"I don't care if numberOfRecords is not available": the only effect is
>suppressing the diagnostic.
I'm not sure that I understand your point. However if you want to build
effective "stateless" server then there is a point in enabling the
to keep the state of the "numberOfRecords" between the pages and not
burden the server with that. You need an informed client to make use of
On the other hand, I am almost ready building my caching support for my
server (caching of "sql used+numberOfRecords") so don't change anything
because of me :).