On Thu, Aug 26, 2004 at 05:53:51PM +0100, Jamie Lokier wrote:We do that, err, it is our design to do that. Hmm, the plugins to do that seem to all be in the next to implement list and not on the implemented already list.....
Rik van Riel wrote:
And if an unaware application reads the compound fileYes, exactly that. The streams are created on demand of course, and
and then writes it out again, does the filesystem
interpret the contents and create the other streams ?
by userspace helpers when that's appropriate which I suspect it almost
always is.
Unless I overlook something (please tell me what), theYes. Hence the idea of coherent views between two files: writing to
scheme just proposed requires filesystems to look at
the content of files that is being written out, in
order to make the streams work.
one affects the content of the other, although the calcalation is only
done on demand (or when the fs wants to migrate the representation --
for example, creating the flat container prior to deleting the
regeneratable pieces in order to save space).
I haven't seen anything from Namesys that says they'll do that.