[aerogear-dev] Client side Paging Spec

[Matthias Wessendorf]

On Thu, Jan 17, 2013 at 11:36 PM, Summers Pittman <supittma at 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

I can see this is handy. Right now it would be always query parameters.
I will update the spec to reflect this.


> 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.

Not really...

The JS version of the read was doing this:
read(page:"next", ......)

the Java/iOS bits were already returning some "paged list", on which
you can invoke next/prev.

How has this changed? Please explain


> 2.a) Paging state (offsetValue, limitValue) will be passed to read and
> not be properties of the pipe.

Again, not seeing a huge change here, since Java/iOS already take a
"read filter", which has the offset, limit etc "configuration"


Regarding 2a, I don't even need to update the spec, since it is
abstract enough to say the "paging" needs some configuration.
Fortunately it does NOT say, how to apply them... so that's up the the
actual impl.


-Matthias



>
>
> 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/specs/abstract_aerogear-client-paging.markdown
>>
>> Please review the document!
>>
>> Cheers!
>> Matthias
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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