Re: Resource Fork - is this a good use/the right thing to do?
Re: Resource Fork - is this a good use/the right thing to do?
- Subject: Re: Resource Fork - is this a good use/the right thing to do?
- From: Daniel DeCovnick <email@hidden>
- Date: Wed, 23 Apr 2008 12:05:38 -0400
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.
-Dan
On Apr 23, 2008, at 11:10 AM, Jens Alfke wrote:
Another possibility is to write a short unique string (like a UUID)
into an extended attribute, and then use that as a key into your own
external data store, like a database or plist you put in some
central place.
A nice feature of this approach is that you only have to modify the
file once, not every time your data changes.
A drawback is that if the file is sent to somebody else, the
information doesn't go with it. (Which, depending on what the info
is, could be considered a benefit: people have gotten in trouble for
forgetting about the metadata Word attaches to their documents.)
—Jens
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden