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. Jim ... > > - In Fastpath (i.e., the static file code) do an internal-redirect to a > compressed file on disk, creating it when it doesn't exist or is stale (i.e., > stat both original and compressed each request which should be fine).
