You find more informations, discusions, bug reports and latest
Currently mod_zipvfs is in first stage, but IMHO in
good usability, features implemented are:
- normal / gzip response sending
This means if browser support deflate Content-Encoding (browser itself uncompress data) mod_zipvfs detect this and send raw data
instead of uncompressed.
- timestams handling
Allow browser to use its internal caching mechanism.
- logical path mapping
As you can expect, for http://localhost/my_doc.zip/path/ mod_zipvfs try to
search index.htm(l) pages in path and if it can't find them print directory
- optional compile time switches for CRC calculations or
Usefull for debugging and testing
Next improvements will be mainly in these areas:
- Sharing open archive bettwen requests (archive pooling)
Now each request open, read and close archive file. Because many resources
links to other resources, repeating opening and closing archive downgrade
performance. Better handling is pooling opened archive between requests for
specificated period of time and use cleaner thread which clean pool if time is
- Better directory listing
Add sorting and look and feel improvements.
- Platform independend
Sources are now compiled on Win32/VisualC envinronment (I started with MinGW
(gcc win32 port) but linker has problems with Apache libraries), next and
first task is porting to all Apache supported platforms.
- Version 0.2 - binary update toward Apache 2.0.43 and higher stable API
- Version 0.1 - first public available version
Win32/VisualC sources only