On Wed, Jan 16, 2013 at 3:01 PM, Kris Borchers
<kris@redhat.com> wrote:
If the data doesn't exist HTTP 204 is a good fit. Just don't understand why we need to interrupt the app workflow, because the data doesn't exist.
I would prefer that an exception is thrown client side before a request is ever sent to the server. That way we save the http request which is important on mobile.
Ah! yeah - good point -> since the "paging API" knows there is no "next" (for instance)
That being said, then the issue becomes what if that page does exist but we don't allow the request because the data was updated since our last read? Then we wouldn't know without another read happening.
yeah - here could the 2.x targeted feature of 'sync' come in…
"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.
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev