[aerogear-dev] Web Linking and Paging

[Daniel Bevenius]

>it was also decided to remove the "offset" and "limit" from the response
headers since that info is in the links. Though I think it could be useful
to still include those headers, I think it can be ok without them.
It would not be a problem to add them if we wanted to. We just need to
decide on it.

>1) Controller should include any and all filtering parameters that were
used to generate the paged result set in the web linking headers.
I agree and must confess that the solution did not take this into
consideration (I bow my head in shame).
I've updated the controller-demo [1] so that it now takes a 'color' as a
query parameter which will also be included in any links returned (at the
moment these are "custom" link headers, but the same will work for Web
Linking).
There are some other changes too on the server side, but describe them in
the appropriate thread [2].

[1] https://gist.github.com/4500336
[2]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Server-Side-Paging-API-with-Metadata-and-Links-was-Re-Paging-Demo-td1270.html





On 18 January 2013 23:24, Kris Borchers <kris at redhat.com> wrote:

> Since we decided to use the Web Linking standard (RFC 5988) for
> controller's paging implementation, it was also decided to remove the
> "offset" and "limit" from the response headers since that info is in the
> links. Though I think it could be useful to still include those headers, I
> think it can be ok without them.
>
> That being said, it got me to thinking about those links. The question
> that occurred to me was whether or not those links included all other query
> params that were used to generate this paged result. I would really hope
> that it did, otherwise these links would be pretty much useless since they
> would link to a paged result of unfiltered items. I just want to verify the
> following items and make sure we're all on the same page:
>
> 1) Controller should include any and all filtering parameters that were
> used to generate the paged result set in the web linking headers.
> 2) If other servers for some reason do not include that information, that
> is not a problem our clients have to deal with. We should be free to assume
> that if the server is use web linking as its paging implementation, it is
> providing the necessary information in that link to get to the next or
> previous page in that filtered set.
> _______________________________________________
> 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/20130120/8e07281f/attachment.html