> > Archives and Compression: > > The new File System will provide transparent management of archive files, > > including recognition, loading, decompression, compression and saving. > > The files will be efficiently mounted into the VFS tree and will be > > accessible as ordinary file within the VFS. Compression and decompression > > will be performed in parallel to file loading, performing on each block > > as it is available, in order to provide minimum latency in the > > loading/saving of compressed files and archives. > > Some things to consider, what would be the syntax? > Let's say you have an archive foo.zip. Do you access it like > .../foo.zip/somefile? Or treat it like a directory, ie .../foo/somefile? > If the latter what happens if there is also a directory "foo" next to > foo.zip, does the dir shadow the zip, the zip shadow the dir, or do they > get merged?
Some good stuff, Just want to add that I prefer ../foo.zip/somefile as opposed to ../foo/somefile since I can find all the zips in a directory (like user installed levels) and just access them with having to perform any name mangling. IMHO I should be able to put a zip file with a missing extension (foo not foo.zip) and it should detect foo as being a zip by reading its magic bytes. I don't think the extension should affect its mount name. Also what about support for other protocols? I'm not saying implement them, just adding support for them so that in the future if someone wanted to code for reading data from that source its there http://xyz.com/a/b/cde/somefile zip://(http://xyz.com/a/b/cde/file.zip)/somedir/somefile Amir Taaki _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
