Am 01.03.2012 um 12:44 schrieb Ralf Nyren:
On Wed, 29 Feb 2012 14:36:16 -0700, Gary Mazz <garymazzaferro@gmail.com> wrote:
Good point, thanks for taking time to explain. We simply leave it up to the client to maintain state on which "page" it has requested last. Protocol-wise paging only exist on the query level then.
I would like to leave the "total collection size" value in the data format though. That way a server still has the option to throttle the response size when necessary.
Something like this then?
"Get 50-entries page _after_ resource xxx": GET /compute/?marker=xxx&start=1&end=51
"Get 50-entries page _before_ resource xxx": GET /compute/?marker=xxx&start=-1&end=-51
"Get 10 resources _including_ resource xxx": GET / compute/?marker=xxx&start=0&end=10
More or less. We have to check inhowfar this needs to be done as parts of the query paramaters, and how this can be sensibly combined with RFC5988 information. -A. -- Alexander Papaspyrou alexander.papaspyrou@tu-dortmund.de