Re: File Manager and FSRefs [was: creating a resource fork and writing raw bytes to it]
Re: File Manager and FSRefs [was: creating a resource fork and writing raw bytes to it]
- Subject: Re: File Manager and FSRefs [was: creating a resource fork and writing raw bytes to it]
- From: Jens Alfke <email@hidden>
- Date: Thu, 22 May 2008 08:21:56 -0700
On 21 May '08, at 11:49 PM, Charles Srstka wrote:
Is it really vital functionality, though? Resource forks have been
deprecated for some time now, and FSRefs, while useful and well-
liked by many users, don't really seem to be on Apple's radar these
days.
There's a ton of other functionality in Files.h besides those. Scroll
through it sometime. The first thing that comes to my mind is the
directory iteration functions, which are (a) the most efficient way to
list directories, and (b) return a lot more information than
NSFileManager (and I think even more than stat.) There's also
PBCatSearch, hands-down the fastest way to find a file on an HFS or
AFP volume.
FSRefs are also highly filesystem-dependent, and HFS+, the only file
system (as far as I know) that currently fully supports them, is
showing its age and ready to be replaced, possibly by a file system
like ZFS that wasn't invented by Apple.
FSRefs work on any filesystem, but they work better on ones that have
stable file IDs that can be used instead of paths. I'm pretty sure ZFS
would fulfill that requirement.
Anyway, this discussion is probably better suited to filesystem-dev at
this point (guess this is my morning for redirecting threads to other
lists...)
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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