[aerogear-dev] Client Paging API Unificaiton thread

[Matthias Wessendorf]

On Wed, Jan 16, 2013 at 5:06 PM, Summers Pittman <supittma at redhat.com>wrote:

>
> Sorry if this dupes, looks like my first message is in limbo.
>
> We agree:
> The Pipe Implementation will have a read(<ConfigObject> , CallBack) method
> Config Object will include pagining information
>
> The biggest difference between our current proposals that I can see is
> where and how are the calculations for Paging done and provided to the
> developer.
> In iOS and JS (from the examples) the User provides and updated
> configObject with an "action" param to the read method.



Not true, for iOS. The proposal was always close the the Java/Android one.

I had a recent updated, and changed the "query page" to be also a "paged
list",

https://gist.github.com/4546737



> In Android the
> response dataSet includes convenience methods which call the pipe using
> the appropriate parameters.
>
> Is that there actually is keeping us from having this thing nailed down?
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130116/1bea04dd/attachment.html