Any one have good strategies on how to deal with state restoration and preservation when your app relies on lots of data from a server and the data may change significantly between app runs?
I watched the video WWDC 2012-Session 208 which talks about state preservation and restoration and I do understand that you're saving and restoring your app's View Controllers and not the data model used by your app.
But when what your view controllers display is very much linked to the data that you receive from a service, some of which are either stale or no longer exists since your app shut down and relaunch, you can't save the object's id and hope to redisplay it at a later time.
Most of the sample apps I've come across seem to cover the simple version where app data is fairly static and doesn't seem to come from a service.
My questions are: 1) What are the gotchas and other caveats one must consider for a client/server style app?
2) With the caveats considered, where in the app would you initiate the call to the remote services to refresh of data?