[aerogear-dev] Client side Paging Spec

[Matthias Wessendorf]

> My suggestion is to name these two parameters something more generic like locator/count where locator=page/offset and count=limit/perPage. Then in our configs we would provide these options:
>
> pagingType {String} - determines the paging method to be used in calculating next page, etc. and could be either "offset" or "page", default "offset"
> locatorParam {String} - locator parameter name, default "offset"
> locatorValue {Number} - page index or offset
> locatorIdentifier {String} - the locator identifier name, default "AG-Paging-Offset"
> countParam {String} - count parameter name, default "limit"
> countValue {Number} - items per page
> countIdentifier {String} - the count identifier name, default "AG-Paging-Limit"
>
> Thoughts?


Any news on this ?

-Matthias

>
> On Jan 17, 2013, at 12:23 PM, Summers Pittman <supittma at redhat.com> wrote:
>
>> 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
>>>
>> +1, let's see how it works in actual implementation!
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> 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