[aerogear-dev] Specification for query RESTFul resources using offset, limit & total

[Kris Borchers]

On Jan 14, 2013, at 1:00 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Morning everybody.
> 
> Daniel has already implemented a lot of cool stuff on AeroGear controller for pagination. For this reason I created this Jira to see if the implementation matches our expectations on the client side (https://issues.jboss.org/browse/AEROGEAR-814).
> 
> For example, currently the headers are returning something like it:
> 
> HTTP/1.1 200 OK
> Content-Type: application/json;charset=UTF-8
> Content-Length: 160
> AG-Paging-Offset: 0
> AG-Paging-Limit: 4
> AG-Paging-Total: 4
> AG-Links-Next: cars?offset=1&limit=4
> AG-Links-Last: cars?offset=3&limit=4
> [
>   {"color":"Green","brand":"Audi","id":1},
>   {"color":"White","brand":"Audi","id":2},
>   {"color":"Black","brand":"Audi","id":3},
>   {"color":"Black","brand":"BMW","id":4}
> ]
> 
> 
> Question, do we really need AG-Links-Next and AG-Links-Last. If I know about the total and I have the fields limit and offset, looks like 'Next' and 'Last' are useless. Am I wrong?

I agree that if you know limit and offset, then those links are not necessary … unless someone is directly parsing the info returned by that endpoint and wants to just generate a link based off of that without building the URL themselves. I would say it's just extra and not necessary.

> I was wondering about something like this http://www.redmine.org/projects/redmine/wiki/Rest_api#Collection-resources-and-pagination
> 
> 
> -- 
> "The measure of a man is what he does with power" - Plato
> -
> @abstractj
> -
> Volenti Nihil Difficile
> _______________________________________________
> 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/20130114/49c75718/attachment.html