On May 18, 2015, at 12:52 PM, Britt Durbrow <bdurb...@rattlesnakehillsoftworks.com> wrote:
> In order to maintain graph coherency the object pool controller must ensure > that there is only ever one object in memory with a particular UUID. > Consequently, I can’t just have the object pool controller release the > objects without assurance that nothing else is going to keep it around (and > potentially use it after the object pool controller has replaced it with > another object with the same UUID, reloaded from disk). Can you have some sort of -invalidate method on the objects that puts them into a state where they can't be used or confused with a subsequently-loaded object? If necessary, it could clear the UUID or whatever. Regards, Ken _______________________________________________ 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
