W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2003

Re: WebDAV on BEA WebLogic (in support of WebCT Vista)me

From: Albert Lunde <atlunde@panix.com>
Date: Tue, 7 Oct 2003 00:41:43 -0400
To: Frank Lowney <frank.lowney@mac.com>
Cc: w3c-dist-auth@w3.org
Message-ID: <20031007044143.GA24449@panix.com>

On Mon, Oct 06, 2003 at 09:15:58PM -0400, Frank Lowney wrote:
> However, I am curious about whether this reasoning applies equally to 
> MacOS X as it does to the preceeding operating system called MacOS 
> Classic.
> 
> Can anyone here comment on the aptness of this "reason" for this 
> phenomena.  After all, the built-in MacOS X facility for WebDAV does 
> not exhibit these symptoms under Apache or WebSTAR webservers.  I was 
> of the impression that MacOS X did not use forked files as Classic 
> did.

MacOSX still supports the use of resource forks and Finder meta-data
(Type/Creator codes and a number of bits), it's just somewhat 
depreciated going forward. Applications ported to OSX using the 
Carbon Framework are more likely to use them for backwards-compatability,
though that's not a hard-and-fast rule. "Bundles" out of the NeXT
heritage, are the flat-file construct that is trying to superceed
resource forks, etc.

HFS+ has native support for Unix permissions, Finder-like attributes,
and resource forks. I think the hack you cite is invoked to support them
on some other file systems.  However, examination of the mkisofs
man page reveals the existence of a dozen or so incompatible schemes
for supporting resource forks and Finder meta-data on non-Apple filesystems.
so a lack of consistency is hardly surprising, I'm afraid...
Received on Tuesday, 7 October 2003 00:41:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:05 GMT