I think you may be mixing these two:
- number of record located by the query
- number of records present in the response
for example your query might have indentified 1000 records, and included 10
in the response. The response parameter numberOfRecord would be 1000. There
is no response parameter saying how many are included in the response (the
client can count them itself) but the request parameter maximumRecords, for
example, 10, say "don't exceed this number".
----- Original Message -----
From: "Roger Wallin" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, July 20, 2007 9:55 AM
I'm writing a very "simple" SRU-server. I'm worried about the response
parameter "numberOfRecords". For me it would seem natural to request for
the "numberOfRecords" only when you need it, fex. by
using "maximumRecords=0". Have I understood this right, although
requesting "small pages" of a large result-set, the answer of the server
should always contain the "numberOfRecords"-response parameter?
Isn't there a way to tell the server that I already know
the "numberOfRecords" and you(=the server) don't have to count them for me?
Any advice appreciated! Caching query and nrOfRecords in application
Background: It's relatively simple to get a limited page from a database,
not necessarily getting the number of records for the whole result-set
within the same Sql-clause.