Re: [aerogear-dev] iOS client side data persistence
On Thu, Jun 6, 2013 at 9:34 PM, Yavuz Selim YILMAZ <yavuzsel(a)buffalo.edu>wrote:
Hi All,
I am trying out the AeroGear iOS lib, and trying to achieve client side
data persistency employing AeroGear as much as possible. Here are a few
questions I have, and I would appreciate any comments, suggestions and/or
directions:
- So, starting from the basic question, how can I retrieve my data stores
once user leaves the app and comes back (or, can I do this at all)?
there are callbacks for the lifecycle of the app
-Then, what is the difference between "MEMORY" type data store and
"PLIST"
type one (especially considering my goal is data persistence)?
MEM -> run of the app;
PList -> property list => pers. storage on the file system (sandbox style)
- Or alternatively, considering what AeroGear provides for now, what would
be the best approach to implement offline support for the client? (for now,
what I know is the lib does not provide DataSync. so data consistency is
what I will take care of on my own.)
store PList and use the "Reachability" class (Apple example OR
https://github.com/tonymillion/Reachability)
-M
Thanks for your time to read (and to respond). Bests,
---
Yavuz Selim Yilmaz
SUNY at Buffalo
Computer Science and Engineering
PhD Candidate
_______________________________________________
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
Attachments:
- attachment.html (text/html — 4.7 KB)