Re: Resurrecting 'Mac OS X "resource fork" support'

Danny Dawson wrote:
> 1. Resource forks are platform-specific.

Seems to me that at least NTFS supports a similar concept:

Every file has a default (unnamed) stream, but you can create
alternate (named) streams on a file easily:

==========================
C:\> echo hello > myfile.txt
C:\> echo goodbye > myfile.txt:mystream
C:\> dir /b my*
myfile.txt
C:\> more < myfile.txt
hello
C:\> more < myfile.txt:mystream
goodbye
==========================

The Security Descriptor, extended attributes and timestamps relate to
the file, and are thus common to all streams.

Other ways of accessing the default data stream include ":" and "::$DATA":
==========================
C:\> echo whee > myfile.txt:
C:\> more < myfile.txt
whee
C:\> echo poop > myfile.txt::$DATA
C:\> more < myfile.txt
poop
==========================

Having a $DATA identifier for the stream data sort of suggests that
the stream has other properties than it's blob. I've never seen any
mentioned / used anywhere. Who knows.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 21 09:49:58 2006