The definition of responsePosition is:
This is the position within the list of terms returned where the client
would like the start term to occur. If the position given is 0, then the
term should be immediately before the first term in the response. If the
position given is 1, then the term should be first in the list, and so
forth up to the number of terms requested plus 1, meaning that the term
should be immediately after the last term in the response, even if the
number of terms returned is less than the number requested.
So, if you request 500 terms and position 501, the server can only return
50, you'll get the 50 immediately before your term, as expected.
Say you ask for 500 terms and position 250, and the server can only return
50 at once. Does the server then position the term at 25? (500/250 -> 50/25)
Say you ask for 500 terms and position 250, and the server can return 300.
Then the server scales 300 to 150, even though it -can- return the term
at position 250?
Rob
,'/:. Dr Robert Sanderson ([log in to unmask])
,'-/::::. http://www.o-r-g.org/~azaroth/
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. University of Liverpool
____/:::::::::::::.
I L L U M I N A T I L5R Shop: http://www.cardsnotwords.com/
|