[Rets-dev] RETS 1.5 spec OFFSET clarification

[JP Fielding]

im pretty sure that it being optional is the case.   not only is paging an
optional feature, i know at least one vendor that has combined this with a
non-optional 5k  row limit on any search (60k actives listings).   this
leaves pulling a complete query an academic problem for the interested
developer.

On 6/14/07, Timothy Frazer <tfrazer at terradatum.com> wrote:
>
>  In the RETS 1.5 spec the following snippet appears for the use of the
> client-optional OFFSET feature in searching:
>
> ***7.4.4 Offset*
>
> The client may specify that a retrieval start at other than the first
> record in the set of records matching he query by specifying the Offset
> argument.*** Offset* ::=*** 1*9DIGI****T. **** * This argument indicates
> to the server that it should start sending the data to the client
> beginning with the record number indicated, with a value of "1" indicating
> to start with the first record…
>
> Does the use of the word "should" in the sentence beginning "This argument
> indicates to the server that it should start sending" mean this feature is
> a server SHOULD implement as opposed to a MUST?  I noticed that "SHOULD"is in caps in the subsequent
> 1.7 spec, in this section, so I'm assuming the OFFSET doesn't have to be
> truly functional.
>
> I'd appreciate any clarification offered.
>
> Thanks,
>
> Tim
>
> _______________________________________________
> Rets-dev mailing list
> Rets-dev at rets.org
> http://lists.rets.org/mailman/listinfo/rets-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20070614/96849992/attachment.html