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: Thu, 24 Apr 2008 02:14:08 -0400
Honestly, I don't care how the data is stored, as long as I've got
some reliable place to store file-specific data such that it can be
reliably tied to the file (cross-user/cross-computer concerns are
primary, cross-platform concerns are secondary - I'm only writing this
for OS X currently, and I could always have export and import
functionality to keep a real file around while the target file gets
sent out and about and then recombine them later). If that means
writing raw binary or XML data to an unformatted resource fork, that's
fine. If that means I've got to put it into a resource with it's own
type, that's fine too (this would be a bit more reliable, I imagine,
as it's possible I'll run into files with other things in their
resource forks already). If that means something else entirely, that's
cool too.
Now, if y'all could explain what a resource map is (the docs don't
show anything meaningful) and why I might be using it, it'd be
appreciated.
-Dan
On Apr 24, 2008, at 12:52 AM, Graham Cox wrote:
On 24 Apr 2008, at 2:46 pm, Chris Suter wrote:
On 24/04/2008, at 2:28 PM, Graham Cox wrote:
On 24 Apr 2008, at 12:59 pm, Chris Suter wrote:
The limits for resource forks are the same as for data forks
Not true - the ResourceMap contains some 24-bit pointers, or at
least it used to, as well as some 16-bit length fields as well.
Unless these have been changed (possible I guess, I don't know)
these will bite you before the file fork limitations do.
I'm sorry, but it is true. We're not talking about ResourceMaps,
we're talking about resource forks. ResourceMaps are just one thing
that you might store in a resource fork but I don't know of any
reason why you can't store anything you like in them and the limits
for a resource fork are the same as those for a data fork.
- Chris
Sure, the fork limitations are the same.
But the OP was talking about storing data in the Resource Fork as a
resource (correct me if I'm wrong, I've only been following the
thread peripherally) so ResourceMaps do come into it.
G.
_______________________________________________
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