Caching the result could save the re-read. However, if your data store (the file) is not opaque to the user someone will edit it and then your cache is out of sync with the file. That may or may not be desirable, but at least it's something to incorporate into the design.
Sandor > On Jan 25, 2016, at 11:50, Dave <d...@looktowindward.com> wrote: > > Hi Again, > >> The *easy* way to do a deep copy is in fact to archive the root object and >> unarchive the result. > > Yes, I’ve come to that conclusion myself thinking about it. Apart anything > else it offloads the problem nicely. In my case, I don’t need to archive it > at all, I just need to load another copy of the same file……… The first load > occurs at App startup and that can take as long as it needs, but I need the > second load to be as fast as possible, this got me to thinking. At the moment > my code does this: > > myNetwork = [NSKeyedUnarchiver unarchiveObjectWithFile:myFilePath]; > > Could I hold the data read here somewhere and use that to save re-reading the > file the second time around? > > Thanks a lot > All the Best > Dave > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/admin.szatmari.net%40gmail.com > > This email sent to admin.szatmari....@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
