Ryan Bloom wrote:

> > The core question is whether we store data in the cache with transfer
> > encodings already applied.
> 
> I would put it before the content encodings, but after the content filters.  My
> reasoning is simple.  Content encodings tend to be fast, but content filtering
> tends to be slow. Cache the slow stuff, ignore the fast stuff.

But from a keep-it-simple point of view, if we make the cache the very
last filter, and then make it behave exactly like a transparent cache,
then we have a good chance that it will "just work", because the HTTP
protocol defines the correct behavior already and transparent caches are
widely deployed.

If we start moving it up and down the filter chain, we're likely to
introduce some nasty what-if's that we have not encoutered before.

Regards,
Graham
-- 
-----------------------------------------
[EMAIL PROTECTED]                "There's a moon
                                        over Bourbon Street
                                                tonight..."

S/MIME Cryptographic Signature

Reply via email to