archive only what changed?

2008-07-07 Thread Randy Canegaly
I have an application whose data model is an NSMutableArray with elements that could be pointers other NSMutableArrays, much like what you would navigate with a NSIndexPath. I am using NSKeyedArchiver to archive the data model to a file. Right now I archive the entire top level array

Re: archive only what changed?

2008-07-07 Thread I. Savant
\On Mon, Jul 7, 2008 at 10:13 AM, Randy Canegaly [EMAIL PROTECTED] wrote: I have an application whose data model is an NSMutableArray with elements that could be pointers other NSMutableArrays, much like what you would navigate with a NSIndexPath. I am using NSKeyedArchiver to archive the data

Re: archive only what changed?

2008-07-07 Thread Andy Mroczkowski
Another possible option is CDBStore framework. I haven't personally used it, but it claims to fill the gap between archiving/property lists and Core Data. http://mooseyard.com/projects/CDBStore/ - Andy On Jul 7, 2008, at 10:25 AM, I. Savant wrote: \On Mon, Jul 7, 2008 at 10:13 AM, Randy

Re: archive only what changed?

2008-07-07 Thread Joan Lluch (casa)
Core Data does a really good job at what you are describing, when using SQLite as a persistent store, although this may not be what are you looking for. The only other approach to this that I think of is to cache the objects that change in your model and then only store these objects