Before investing a lot of time/energy into storing the gzip results,
someone may want to do some benchmarks. For a low-volume site,
nothing matters. On a high-volume site, storing a large cache of gzip
results on disk will put more pressure on the memory subsystem.
If someone decides that storing the gzip results on disk is a good
thing, the cache size and all that should probably be a config parameter,
and an option for disabling it altogether would be good (cache size of
zero maybe). Static file handling would also need to check the mime
type and not compress images and other already-compressed data.
Ah - good point. Another option is to use some other server for static content which does the right thing, leaving AOLserver for the dynamic parts. That's what we do although I know most folks mix the static and dynamic on the same server. AOLserver's threaded architecture isn't great for static content - I wouldn't expect Apache's multiprocess or newer multithreaded architectures are any better. Single threaded or kernel-based approaches work better.
-Jim
