Re: NEW ISSUE Can a Client Set the Page Size?

I was not asserting that it did, Ashok.
Just relaying history and (having said we held it out) why we did so.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario


Ashok Malhotra <ashok.malhotra@oracle.com> wrote on 02/21/2013 02:44:33 
PM:

> From: Ashok Malhotra <ashok.malhotra@oracle.com>
> To: public-ldp-wg@w3.org, 
> Date: 02/21/2013 02:45 PM
> Subject: Re: NEW ISSUE Can a Client Set the Page Size?
> 
> This does not address the issue which is to allow the client to 
> control the page size
> as he moves from one device to another.
> All the best, Ashok
> 
> On 2/21/2013 5:36 AM, Wilde, Erik wrote:
> > hello john.
> >
> > On 2013-02-13 14:09 , "John Arwe"<johnarwe@us.ibm.com>  wrote:
> >> We had trouble enough getting consensus amongst our own product 
groups
> >> (Erik's "very bad" flaw being one I raised) about the paging approach
> >> generally that we chose to simplify by omitting it from the 
submission.
> >> We can't
> >> solve everything in a single go and still have it finish soon enough 
to
> >> be relevant, so we put it on the "good follow-on discussion" pile.
> > just as a follow-up: while client-controlled paging (requesting 
specific
> > page sizes and specific pages) gets a little more involved when it 
should
> > be done RESTfully (because these request parameters probably should be
> > exposed via URI templates), the "cheap" solution is much easier. for
> > server-controlled paging, there simply can be "next" and "previous" 
links
> > (and a few more) exposed in a way similar to
> > http://tools.ietf.org/html/rfc5005 . in this case, no templates are
> > required, but clients still can happily page through results (but they
> > cannot control the paging process, or request specific pages).
> >
> > cheers,
> >
> > dret.
> >
> >
>