<br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 5:06 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Sorry if this dupes, looks like my first message is in limbo.<br>
<br>
We agree:<br>
The Pipe Implementation will have a read(<ConfigObject> , CallBack) method<br>
Config Object will include pagining information<br>
<br>
The biggest difference between our current proposals that I can see is<br>
where and how are the calculations for Paging done and provided to the<br>
developer.<br>
In iOS and JS (from the examples) the User provides and updated<br>
configObject with an "action" param to the read method. </blockquote><div><br></div><div><br></div><div>Not true, for iOS. The proposal was always close the the Java/Android one.</div><div><br></div><div>I had a recent updated, and changed the "query page" to be also a "paged list",</div>
<div><br></div><div><a href="https://gist.github.com/4546737">https://gist.github.com/4546737</a></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In Android the<br>
response dataSet includes convenience methods which call the pipe using<br>
the appropriate parameters.<br>
<br>
Is that there actually is keeping us from having this thing nailed down?<br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>