[aerogear-dev] Paging Metadata in Response Body

[Kris Borchers]

[Reposting from GMail because Red Hat account is blocked again]
Thinking more, we could probably just keep the defaults undefined, that way they only define if they need them, otherwise the root of the response is assumed which would probably work better since for example, Twitter encapsulates the data but the paging is at the root of the response.

On Jan 21, 2013, at 3:19 PM, Kris Borchers <kris at redhat.com> wrote:

> I've hit one small snag. If the paging metadata is returned in the body, it would probably be useful for the developer to be able to specify a "paging container" and/or a "results container" since each of those pieces of information would probably be encapsulated from the other in any sane server implementation. I would suggest something like metadataContainer and dataContainer with defaults of "paging" and "data" as defaults but I am totally flexible on those.
> 
> Thoughts?
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev