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.