4 ms·
If you use CoreData (and you should) you can get the same effect by using a NSFetchedResultsController. http://developer.apple.com/library/ios/#documentation/Co
by pkaler 15y ago
If you use CoreData (and you should) you can get the same effect by using a NSFetchedResultsController.
http://developer.apple.com/library/ios/#documentation/CoreData/Reference/NSFetchedResultsController_Class/Reference/Reference.html http://developer.apple.com/library/ios/#documentation/CoreDa...
The advantage of using Parse is that it syncs the local store with the store on the server. However, if your server exposes a RESTful API, it isn't too difficult to sync by writing up a bunch of closures using NSURLConnection+BlocksKit.h.
https://github.com/zwaldowski/BlocksKit/blob/master/BlocksKit/NSURLConnection+BlocksKit.h https://github.com/zwaldowski/BlocksKit/blob/master/BlocksKi...
- bjtitus 15y agoParse's SDK makes the syncing significantly easier. I tried a combination of REST + CoreData and also a locally running version of CouchDB replicating with a CouchDB server. Parse was by far the simplest to implement and comparatively surprisingly fast. The Parse team has done a great job so far and I'm excited to see what other improvements they make. This little exercise is a good intro to their platform.
- jawngee 15y ago> If you use CoreData (and you should) Can you qualify why you should use CoreData? Every project I've "rescued" for clients that had CoreData beginnings eventually got ripped out for an easier SQLite/simple entity solution.