Re: creating a resource fork and writing raw bytes to it
Re: creating a resource fork and writing raw bytes to it
- Subject: Re: creating a resource fork and writing raw bytes to it
- From: Mike Fischer <email@hidden>
- Date: Thu, 22 May 2008 09:35:36 +0200
Am 22.05.2008 um 08:49 schrieb Charles Srstka:
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.
Certain parts of Apple have never had them on their radar,
unfortunatly ;-) Still they have seen steady improvement and don't
have that rotten smell that some other APIs seem to aquire as of late.
FSRefs are also highly filesystem-dependent,
They are? That's news to me. In what way?
and HFS+, the only file system (as far as I know) that currently
fully supports them,
I think you might be confusing the API with features of the file
system? Apple has done a fairly good job of simulating missing
feature on file systems that make this necessary. FinderInfo and
Resource Forks come to mind. They work fine on FAT, SMB, ISO9660, ...
is showing its age and ready to be replaced, possibly by a file
system like ZFS that wasn't invented by Apple.
So? That's just another file system that might or might not support
certain features natively. The API should protect you from these
differences.
The only thing the File Manager API is missing is good support for
POSIX functionality like symbolic & hard links and unlink(2).
Mike
--
Mike Fischer Softwareentwicklung, EDV-Beratung
Schulung, Vertrieb
Note: I read this list in digest mode!
Send me a private copy for faster responses.
_______________________________________________
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