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

Ashok, I don't see anything addressing this point in the submission.
What we did ourselves as a starting point was define a URL query parameter 
(pageSize) that clients can use as a hint to the server (ala Accept). 
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.
I don't think trackbot will transmogrify "NEW ISSUE" into the actual 
issues list, so if that was your intent you'll likely be disappointed. 
We'd want to link this thread to it anyway, so if you think it's worth a 
first-release discussion then open a new issue and respond to the list 
with "Issue-nn" in it so the bots can do their thing for us.

Best Regards, John

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




From:   "Wilde, Erik" <Erik.Wilde@emc.com>
To:     "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, 
Cc:     "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>
Date:   02/13/2013 07:22 AM
Subject:        Re: NEW ISSUE Can a Client Set the Page Size?



hello all.

On 2013-02-13 00:47 , "Ashok Malhotra" <ashok.malhotra@oracle.com> wrote:
>Page size (number of entries on a page) may need to be changed depending
>on the display device.  How can the client do this?

usual REST patterns would suggest to use URI templates, so that the
service exposes its capabilities declaratively, and then the client knows
how to compose a request given that template, and concrete variable 
values.

https://github.com/dret/I-D/blob/master/template-desc/td-paging-01.xml
shows how this could be exposed RESTfully, based on a draft i am working
on (http://tools.ietf.org/html/draft-wilde-template-desc-00). i am
actively working on this one because of the many template-driven services
that are out there, and often aren't properly link-driven, but instead
rely on hardcoding URI templates either in clients (very bad) or media
types (not quite as bad, but also unnecessarily restrictive).

cheers,

dret.