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: Matt Gough <email@hidden>
- Date: Wed, 23 Apr 2008 15:01:49 +0200
I'd second that. The OS (well, Finder) also adds things to the
resource fork of files (custom icons, info about which app to open a
file with when you changed it from the default etc). Just as long as
you respect the existing contents this is exactly where you should put
your data.
On 23 Apr 2008, at 14:29, Ken Thomases wrote:
On 23/04/2008, at 5:41 PM, Daniel DeCovnick wrote:
Thanks for the suggestion. I've just looked through them now, as
well as at the OSXBook (Mac OS X Internals: A Systems Approach by
Amit Singh) info on that. In theory it looks good, but it's
somewhat confusing. It looks like, at least in 10.4, except for the
resource fork which is mapped as a fake xattr, you can only have
inline attributes, with a length limit of 3802 bytes, and it would
be quite common for my data to be significantly larger than that.
Does anyone know if that's changed for 10.5?
I say, if using the resource fork works for you, go for it.
Whatever disadvantages there might be are 1) theoretical, and 2) no
worse than extended attributes.
No sense bending over backward to try to get some supposedly
superior solution to work not quite as well as the resource fork
would.
That's my two cents, anyway.
Cheers,
Ken
_______________________________________________
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
_______________________________________________
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