<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 11, 2013, at 7:54 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Fri, Jan 11, 2013 at 2:11 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br><blockquote type="cite">on my pagingContext, the next() would figure out how to use it for scrolling.<br><br>I don't mind the headers, actually I like it.<br></blockquote><br>I *think* adding the meta data into the response would be wrong (cross<br>cutting concerns)<br></blockquote><div><br></div><a href="http://search.twitter.com/search.json?q=aerogear">http://search.twitter.com/search.json?q=aerogear</a></div><div><br><blockquote type="cite"><br>-M<br><br><br><blockquote type="cite"><br>```<br>Link-Previous: cars?page=0&page=4<br>Link-First: cars?page=0&page=4<br>MetaData-PerPage: 4<br>MetaData-Page: 0<br>Link-Next: cars?page=1&page=4<br><br><br>Do you think we "need" a "Link-Last"? (like github does)?<br><br>-M<br><br><br>On Fri, Jan 11, 2013 at 1:48 PM, Daniel Bevenius<br><<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br><blockquote type="cite">Just to mention it, the Header are on option, we could still return the<br>metedata an links in the json. Perhaps with an extra query param to enable<br>this addition. But I understand that we need to be able to handle headers<br>also if that is what users choose.<br><br><br><br><br>On 11 January 2013 13:46, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:<br><blockquote type="cite"><br>There were some discussions a long time ago but I don't remember ever<br>coming to a conclusion on how paging should be implemented and I don't know<br>any links to gists off the top of my head.<br><br>That being said, this and the Paging Demo thread have gotten me thinking<br>that though I thought JS was ready, I see it is not. I had not thought about<br>the metadata being in headers. Since we are abstracting away the HTTP<br>request, it may make it harder to get at that information without us<br>providing an API into it (well, maybe not for JS but it might be nice to<br>have a built in way to access that info).<br><br>I think this deserves a more in-depth conversation than can happen in<br>e-mail. Anyone up for a hangout ASAP to iron out what we want for the client<br>APIs? This looks like it could get messy when trying to keep it flexible for<br>the developer, though, this does make a great case/example for how useful my<br>ideas for automatic client configuration come in. :)<br><br>On Jan 11, 2013, at 5:39 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>wrote:<br><br><blockquote type="cite">Hi,<br><br>was there already some discussion (and proposal) for paging APIs on the<br>client ?<br><br>It would be nice if the public client API semantics are somewhat<br>identical on the different platforms.<br>(I guess it's a MUST :))<br><br>Any pointers to gists etc are welcome<br><br>Thx<br><br>--<br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote><br><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br><br></blockquote><br><br><br>--<br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a><br></blockquote><br><br><br>-- <br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></body></html>