Re: [aerogear-dev] Pagination Requirements Spec

On Fri, Jan 18, 2013 at 4:04 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: > > > On Jan 18, 2013, at 9:03 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; wrote: > > >But I guess we (at least on the client) are ignoring the FIRST/LAST, right ? > So should we only provide previous/next where it makes sense and remove first/last? > > > +1 +1 > > > > > > > On 18 January 2013 15:57, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >> >> NICE !!! >> >> But I guess we (at least on the client) are ignoring the FIRST/LAST, right ? >> >> :) >> >> -M >> >> On Fri, Jan 18, 2013 at 3:55 PM, Daniel Bevenius < daniel.bevenius(a)gmail.com&gt; wrote: >>> >>> Hey, >>> >>> there was some talk yesterday on IRC about what should be returned by AeroGear Controller if you go beyond past the last page. There was talk of responding with "204 No Content" with an empty body, or responde with "200 OK" and a body containing an empty array (in the case of returning a JSON responds). >>> >>> I've update the controller-demo with the "200 OK" version, but let me know if this should be changed. >>> >>> "Paging" beyond the last page of Cars >>> >>> curl -i --header "Accept: application/json" " http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/cars?of... " >>> >>> HTTP/1.1 200 OK >>> AG-Total: 16 >>> AG-Links-First: cars?offset=0&limit=5 >>> AG-Links-Last: cars?offset=11&limit=5 >>> Content-Type: application/json;charset=UTF-8 >>> Content-Length: 2 >>> >>> [] >>> >>> >>> >>> gist: https://gist.github.com/4500336 >>> >>> >>> On 17 January 2013 17:39, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>> >>>> On Thu, Jan 17, 2013 at 05:10:56PM +0100, Matthias Wessendorf wrote: >>>> > On Tue, Jan 15, 2013 at 11:55 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>> > > standards++ >>>> > >>>> > Looks like we agreed on using the RFC 5988 for the linking. >>>> > >>>> > I think we "just" need to decide on the actual values... >>>> > >>>> > 1) the standard uses "previous" and "next" >>>> no-brainer - let's follow the standards >>>> >>>> -- qmx :) >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev