On Mon, Aug 25, 2008 at 6:56 AM, Graff <[EMAIL PROTECTED]> wrote: > I have a large class I'm archiving that I would like to lazy-load. It's > basically a wrapper around a NSArray and what I'd like to do is load some > instance variables but leave the array archived until a later time in order > to save time and memory. > > When I implement the NSCoding protocol methods initWithCoder: and > encodeWithCoder: is it a bad idea to de-archive the keys that I need and > just retain the NSCoder object so that I can later de-archive the NSArray? > Is there any problem keeping the NSCoder object around for long periods of > time? Is there a better way of doing this?
Core Data ? _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]