[aerogear-dev] Client Paging Strawman

[Matthias Wessendorf]

On Thu, Jan 17, 2013 at 3:56 PM, Kris Borchers <kris at redhat.com> wrote:
>
> On Jan 17, 2013, at 8:41 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
>> On Thu, Jan 17, 2013 at 3:24 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>>> "sync" is probably going to be the option here but ,
>>> what about a setting to say don't go to the server if there is no next/prev,
>>> defaults to always "refresh"
>>>
>>> If they are using our data manager stuff also,  the paging could be based
>>> off that,  probably a whole other discussion(offline?).  I guess i'm
>>> thinking of an app where the data doesn't change often and the user gets it
>>> all up front first.
>>
>>
>> I don't see this being part of 1.0.0. BUT the general paging APIs
>> (e.g. 'next', previous etc) would work on a data store as well, right
>> ?
>
> This will have to be a bigger discussion as keeping things in a particular order in conjunction with things like localStorage or JS objects in general is not trivial.

indexed list ? :)

>>
>> -M
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> 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