12Feb03 Brian Theado - I couldn't find this without looking at the source code, so I thought I'd document it here. Of the above, only mk4 and ftp are fully writable vfs's. The rest are readonly.
Vince - That's right, and mk4 has configurable writability, although it isn't exposed to the user. We need to define an appropriate interface there to say whether a starkit/starpack is read-only, translucent or fully read-write.
NB. There's no reason why the webdav, ns and tar filesystems can't be read-write, if people contribute the code.
13feb03 jcw - FWIW, here is a Tcl package to create a ZIP archive from scratch. This does not allow modifying ZIPs, it just writes a fresh one from start to finish:
http://www.equi4.com/critlib/zipper.README
http://www.equi4.com/critlib/zipper.tcl(It's in critlib for no good reason, really)
The other new development is support for reading compressed data on-the-fly. This is not implemented as a Tcl stacked channel, but it has the same effect: you give it a channel, and you get back a new channel handle (read-only for now). It's actually slightly more involved because you also have to pass the size of the file, both in compressed and in expanded state (this is needed for "seek to end"). See "vfs::zstream" proc in TclVFS "vfslib.tcl". This might be used to adapt the existing .tar reader to work with .tar.gz files.