OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Iterator ID.


A searchResponse may contain a <pso> but always contains an <iterator>. 

An <iterator> has an "ID" attribute and may have "count" and 
"totalCount" attributes.
- "count" represents the number of objects in the result set that the 
<iterator> represents.
- "totalCount" represents the number of objects that matched the <base> 
and <select> elements of the <query> in the <searchRequest>.

A requestor specifies the <iterator> that was output of a 'search' 
operation as input to an 'iterate' operation.  In response to an 
<iterateRequest>, a provider returns another <searchResponse> that 
contains the next <pso> and an <iterator>.

Can the iterator ID change as the requestor iterates a result set?
For example, assume that the original <searchResponse> contains
    <iterator ID="003" count="27" totalCount="27"/>
and the requestor specifies this element in an <iterateRequest>.
Can the provider now return a <searchResponse> that contains
    <iterator ID="004" count="27" totalCount="27"/>?

Darran thinks that the ID must remain constant during iteration (i.e., 
any two iterators that represent the same result set should have the 
same ID), but I didn't come across anything that said so.

Opinions? Recollections?

gpc



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]