Hi Quincey > Yes, I remember the discussion about this scenario: when the managed object > represents a *future* permanent resident of the Core Data object graph. > Outside of a discussion of that scenario, I wouldn't necessarily call this a > "temporary" object. > > In the OP's scenario, there is no suggestion he was trying to keep his > temporary object out of the user interface. (In fact, his later clarification > suggests the opposite.) That's why I was asking if the simple create > it/delete it pattern wouldn't work.
I would agree, in that case, it could be equally valid. The only other benefit I have found in using a dictionary, with the category, is the simplicity of copying the state to and from the original object. But, I wouldn't make a doctrine out of it :-) Joanna -- Joanna Carter Carter Consulting _______________________________________________ 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 arch...@mail-archive.com
