In a message dated 01-09-04 19:17:25 EDT, Ian writes...
> > ASIDE: You really only need the 'compression' part of it. You
> > are a Server, not a client.
>
> we also can be a client.
> think mod-proxy
What current ( or future ) operation would require mod_proxy
to 'decompress' something? I would imagine that if mod_proxy
can ever accept Content-Encodings it would do what SQUID
does... it just stores the response and pays attention to the
'Vary' headers and such but there's never a need to 'decompress'
anything.
Maintaining an 'object compression' cache is a bit different from
regular caching and has to follow different 'rules'. Even if there is
a way to store both a compressed and non-compressed version
of the same URL in a cache there still isn't any real need to
'decompress' anything.
Transfer-encoding: gzip, chunked or some other 'hop to hop' deal
is a different story but there's still no known browser that can handle
that ( nor any known Proxy that can, either, AFAIK ).
It was just a thought.
If people think that ZLIB is 'too big' you can easily cut it in
half by only including what you need.
Ian... are you a committer?
What do you say about adding ZLIB to Apache source ASAP.
Yea or nay?
Yours...
Kevin Kiley
