[aerogear-dev] Pagination Requirements Spec

[Daniel Bevenius]

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?offset=200&limit=5"

HTTP/1.1 200 OKAG-Total: 16AG-Links-First:
cars?offset=0&limit=5AG-Links-Last:
cars?offset=11&limit=5Content-Type:
application/json;charset=UTF-8Content-Length: 2
[]



gist: https://gist.github.com/4500336


On 17 January 2013 17:39, Douglas Campos <qmx at qmx.me> 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 at qmx.me> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130118/a3755fcc/attachment.html