[aerogear-dev] Client Paging Strawman

[Summers Pittman]

----- Original Message -----
| From: "Kris Borchers" <kris at redhat.com>
| To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
| Sent: Wednesday, January 16, 2013 4:29:13 PM
| Subject: Re: [aerogear-dev] Client Paging Strawman
| 
| 
| Maybe this is a server implementation thing or maybe a non-issue and
| I'm just being dense but how would I get the last page as soon as my
| app loads without doing two read() requests? I can get the first
| page by just adding a firstPage (just and example name) config param
| to my paged pipe but I have no idea what the last page would be at
| that point. Thoughts?
| 
On the one hand, -1 is often used for the last element in many APIs. 
On the other hand, to qmx's point, What happens if we are paging digits of PI?
| 
| 
| On Jan 16, 2013, at 11:48 AM, Summers Pittman < supittma at redhat.com >
| wrote:
| 
| 
| 
| 
| On 01/16/2013 12:44 PM, Matthias Wessendorf wrote:
| 
| 
| I tweaked the iOS API a bit more:
| https://gist.github.com/cbff741b3b21a50c3b67 Should AGFilterConfig.
| scrollingMetaDataLocation perhaps be a Pipe level thing (like
| encoding or authentication) instead of a request level thing? I
| don't imagine it changing during the lifetime of a Pipe?
| 
| Otherwise looks really good!
| 
| 
| I also updated the "comparison" gist: https://gist.github.com/4546737
| Feedback welcome....
| 
| On Wed, Jan 16, 2013 at 4:28 PM, Sebastien Blanc
| <scm.blanc at gmail.com> wrote:
| 
| the timeout parameter would be a general property of read() and not
| related
| to Paging ?
| 
| 
| On Wed, Jan 16, 2013 at 4:25 PM, Summers Pittman
| <supittma at redhat.com> wrote:
| 
| On 01/16/2013 10:23 AM, Bruno Oliveira wrote:
| 
| Good point Summers. Might be an obvious question, but there we go.
| Are
| we planning to include timeout as parameter? For example: I want to
| retrieve
| a list of a bazilion users, and I want to specify the timeout
| acceptable to
| wait.
| 
| I didn't get the chance to look at each API, just double checking
| here. +1
| 
| I was thinking about this yesterday.  I want to  but was hoping we
| could
| get the "shape" of the API nailed down first before we started
| hammering
| on specifics.
| _______________________________________________
| aerogear-dev mailing list aerogear-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/aerogear-dev
| _______________________________________________
| aerogear-dev mailing list aerogear-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/aerogear-dev
| _______________________________________________
| aerogear-dev mailing list
| aerogear-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/aerogear-dev
| 
| 
| _______________________________________________
| aerogear-dev mailing list
| aerogear-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/aerogear-dev
|