- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 05 Sep 2014 08:18:55 +0200
- To: Sandro Hawke <sandro@w3.org>, "Roy T. Fielding" <fielding@gbiv.com>
- CC: Martin Thomson <martin.thomson@gmail.com>, Eric Prud'hommeaux <eric@w3.org>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014-09-05 05:18, Sandro Hawke wrote: > ... > The actual driving force behind this I-D is not about using 303s to deal > with httpRange-14, it's to deal with paging. That is, the client does a > GET on A, including these request headers: > > Prefer: contents-of-related > Prefer: return=representation; max-triple-count="100" > > and now the server can directly provide the first hundred triples, via a > representation of B, which is that the first "page" of A. > ... I'll mention again that it continues to confuse me that you're trying to address paging and "see other" with the same mechanism. WRT paging: why don't you use a custom range (<http://greenbytes.de/tech/webdav/rfc7233.html#range.units.other>) such as in: Range: triples=100 ? Best regards, Julian
Received on Friday, 5 September 2014 06:19:31 UTC