On Thu, Jan 17, 2013 at 11:36 PM, Summers Pittman <supittma(a)redhat.com> wrote:
Kborchers and I were on chat and have the following things to
comment
on/finalize
1)Add some options to PipeConfig to indicate whether paging information
is sent as headers, as query parameters, or as body data
Oh. wait...
this is "paging config" (e.g. a JAva-ish read filter) - or "pipe
config" (a pipe config object) ?
-Matthias
and
2) the result from Pipe.read will include the next and previous
methods. Previously we had been discussing have read take a parameter
"next","prev" etc.
2.a) Paging state (offsetValue, limitValue) will be passed to read and
not be properties of the pipe.
On 01/17/2013 11:37 AM, Matthias Wessendorf wrote:
> Hi,
>
> based on today's IRC and mailing list discussions, I have polished the
> client side paging spec:
>
>
https://github.com/aerogear/aerogear.org/blob/client_paging_spec/docs/spe...
>
> Please review the document!
>
> Cheers!
> Matthias
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf