A better solution might be to automatically add the Accept-encoding: gzip to
all upstream requests and flag the file on disk as being compressed using
gzip and if a client doesn't support gzip automatically gunzip it
on-the-fly... make the web servers compress the data for us. :)
We could also leave a background process walking the storelog looking for
uncompressed files matching a pattern (why compress the uncompressible?) and
compressing them, but I'd suggest leaving that alone for now.
-----Original Message-----
>So why not simply compress all data which goes into the cache and like you
>said, uncompress it for clients which do not pass the Allow-Encoding or
>Transfer-Encoding headers.
>
>This would be far better than compressing an object over and over and over
>again, since gunzip uses far less CPU than gzip.
>
>The side benefit is that you could store a lot more in your cache :)
