Re: Cocoa stripping resource forks: does Jaguar fix?
Re: Cocoa stripping resource forks: does Jaguar fix?
- Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
- From: Kirk Kerekes <email@hidden>
- Date: Wed, 3 Jul 2002 09:38:54 -0500
On Tuesday, July 2, 2002, at 10:57 PM, email@hidden
wrote:
From: Cryx <email@hidden>
On Tuesday, July 2, 2002, at 03:00 PM, Kirk Kerekes wrote:
I knew that someone would leap in to defend the indefensible.
We are not working on a BSD system here, even though one is buried
underneath. We are working on a HFS+ filesystem that explicitly
supports resource forks.
Wrong. You may be using HFS+, but certainly not everyone else is using
it.
99.9% of Mac users (your market) are using it. Anybody here format their HD
as UFS?
I didn't think so.
You are also assuming that OS X systems don't have to unknowingly
interact with foreign and remote filesystems.
Sure they do -- just like they have been doing all along. The MacOS didn't
start with Cocoa, you know -- it has been around longer than 'step. There
is a whole set of nice, mature, well-documented tools for safely handling
multi-forked files in a single-fork environment. Cocoa's crime is that it
has totally ignored the issue -- it doesn't even acknowledge that forked
files exist. This is a major shortcoming on Cocoa's part, and it needs to
be _fixed_ instead of denied.
And that pretty much ends the discussion. When working inside this
filesystem, it is reasonably to be expected that everyone plays by the
rules of the filesystem, and doesn't just haphazardly throw user data
away without notice.
Yes, the discussion is over -- only if you honestly believe that the
"let's live on our superior island and damn the rest of the inferior
world" has done anything but shrink Apple's market share. In a
hetrogeneous network built on open standards (ie. the Internet, many
offices), you don't know the remote filesystem type. The lowest common
denominator must be supported until the rest of the world catches up.
Straw-man again. Supporting resource forks doesn't mean that you fail to
support single-forked files, your "lowest common denominator" format. It
just means you aren't _limited_ to them.
There are industry-wide standards for dealing with forked files
(AppleSingle/AppleDouble), and these standards include "magic cookie"
values for identification by alien filesystems. Every competent webserver
package supports and recognizes applesingle/appledouble.
Even Cocoa's Darwin underpinnings understand forked files.
It is time for Cocoa to 'get with the program'.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.