W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: issue 85 - range unit extensions

From: Kris Zyp <kris@sitepen.com>
Date: Fri, 29 Aug 2008 14:16:04 -0600
Message-ID: <062e01c90a14$10e422a0$4200a8c0@kris>
To: <ietf-http-wg@w3.org>
I was referred to this discussion since it sounds like there consideration for deprecating alternate range units. I just wanted to let the group know that Dojo is currently using an range unit "items" for doing paged requests with it's JSON REST client. The HTTP specification makes it sound like this is the most appropriate technique for doing paged/range requests (and the byte unit will not do, it would result in invalid JSON). I believe we are doing something similar to what is mentioned in the referenced article: http://msdn.microsoft.com/en-us/magazine/cc301869.aspx (we could change to "rows" if desired).

When Dojo wants to have paged set of JSON objects (used in the Dojo Grid) it will create a request like:
GET /Customer/
Range: items=-19

And expects servers that are aware of the "items" range unit to respond with something like:
GET /Customer/
Content-Range: items 0-19/244
[{name:"item one"},{....

Thanks,
Kris
Received on Friday, 29 August 2008 20:17:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:54 GMT