I'm creating an iOS application that has a Twitter-like feed of data. I'm currently planning on storing the data on Parse. However, what is the most efficient way to store retrieved objects locally for use when there does not exist a network connection? It sounds like using Core Data is overkill since I'm storing the data on Parse anyway. Can the Parse caching system do this for me or is there something else more appropriate? On a similar note, is there a simple way to check if this locally saved data is up-to-date?
-
Why don't you ask your question on the "Parse Help & Community" board?Hot Licks– Hot Licks2014-01-30 23:11:09 +00:00Commented Jan 30, 2014 at 23:11
-
I have posted several questions here and on the Parse community board. I get much better help here.LostInTheTrees– LostInTheTrees2014-02-27 15:56:56 +00:00Commented Feb 27, 2014 at 15:56
2 Answers
Parse has the capability to cache objects locally. If your app can tolerate the characteristics of caching, then just use that.
My own app will not, so I am using CoreData as my local store. My app has to be able to operate fully when disconnected from Parse, so I have to have something more than cached data. I looked at FTASync and found the concept very useful. When I got into the code though I realized I needed something much more robust, so I have ended up doing a completely new utility to sync Parse with CoreData. This is a huge job, so don't take it on unless your need is commensurate.
-Bob