But the resource fork idea has the same issue if someone uses/sends/writes to the file from the other 90% of the computers on the planet... (windows). Doesn't it?
I think you're best tracking the info in your own data source, doing your best to track and keep up with the user changing it outside your world, and leaving the original file alone. But like all the other suggestions here, that's just one opinion :) > From: Daniel DeCovnick <[EMAIL PROTECTED]> > Subject: Re: Resource Fork - is this a good use/the right thing to do? > > That's pretty much option 1, albeit implemented slightly more robustly > than I was thinking of. But my data's not sensitive, so there's no > advantage in losing it on sending it to someone else, and in fact I'd > much prefer it was retained if possible. _______________________________________________ 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]
