Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Resource Fork - is this a good use/the right thing to do?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Uli Kusterer <email@hidden>
Date: Wed, 23 Apr 2008 20:25:39 +0200

Am 23.04.2008 um 17:10 schrieb Jens Alfke:

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.

Not a good idea. The user could duplicate the file, and then both files would be associated with the same store entry...

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de

_______________________________________________

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



References:  
  >Resource Fork - is this a good use/the right thing to do? (From: Daniel DeCovnick <email@hidden>)
  >Re: Resource Fork - is this a good use/the right thing to do? (From: Jens Alfke <email@hidden>)
  >Re: Resource Fork - is this a good use/the right thing to do? (From: Daniel DeCovnick <email@hidden>)
  >Re: Resource Fork - is this a good use/the right thing to do? (From: "Adam R. Maxwell" <email@hidden>)
  >Re: Resource Fork - is this a good use/the right thing to do? (From: Jens Alfke <email@hidden>)




Prev by Date:
Re: QTMovie grabing while playback

Next by Date:
awakeFromInsert rules: ok to fetch and create other managed objects?

Previous by thread:
Re: Resource Fork - is this a good use/the right thing to do?

Next by thread:
Re: Resource Fork - is this a good use/the right thing to do?

Index(es):

Date
Thread