- From: Miroslav Vodslon <miroslav.vodslon@gmx.de>
- Date: Fri, 2 Oct 1998 06:11:15 -0400 (EDT)
- To: Benoit Mahe <Benoit.Mahe@sophia.inria.fr>
- CC: www-jigsaw@w3.org
Benoit Mahe wrote: > First of all, this feature was not supposed to be really used by > users (I made it for fun), I work with Linux by choice and with MS-OSs by necessity. I have a large disk (but not large enough at all :-) and want all my OSs to share data, including java-bytecodes and my local www mirrors (I need those, for I have an expensive and slow phone link to my ISP). All this condemns me to large FAT partitions (the only file system supported by all the OSs). They waste an enormous space if filled with many small files. I don't think this situation is unique, so maybe zip-browsing with Jigsaw is going to be used by other people... > [...] This week I fixed many bugs, so you may have > no problem with the next release (released this evening). Looking forward to it. [...] > You're zipidx is a org.w3c.jigasw.zip.ZipIndexer, isn't it? It is. > Just to be sure you know it: *default* should be in the directory node. It is. [...] > > zipidx has some extensions as well: gif, htm, html, txt. They all have > > ZipFrames. > > And they are ZipFileResource I guess. Yes. [...] > Automatic things should be done by indexers, not manually. May be > this feature is not described enough in the documentation. > (Ceci dit, toutes les critiques sont les bienvenues ;-) (Alors c'est un plaisir... :-) Encouraged by this, I would still suggest that the non-automatic part of Jigsaw's state, such as the definitions of indexers, be made human-readable, emacs+diff+sed+awk-editable, RCS-versionable and Jigsaw-loadable for those administrators who wish to work that way. Just something to add to a wish-list. If a scripting language is needed, my preference goes to a Scheme that can be both interpreted and compiled to java bytecodes, such as Kawa by P. Bothner of Cygnus and others. Have a nice day, Miroslav.
Received on Friday, 2 October 1998 06:27:56 UTC