I agree with this. Our current AP_FTYPE_* classifications is not granular enough to
support this but that is easily fixed. Patch on the way...

Bill

> A transfer encoding isn't a byterange or chunking output.  It's a compression
> scheme, and that we _want_ to cache, to avoid the cpu overhead.
>
> Handler (e.g. Core/autoindex/mod_webapp etc)
>  V
> Includes and other Filters
>  V
> Charset Translation (Transform to Client's preference)
>  V
> Content Encoding (gz) (Body - large packets - higher compression)
>  V
>  X <<< cache here
>  V
> Byterange
>  V
> Chunking
>  V
> Headers
>  V
> SSL Crypto
>  V
> Network I/O
>
>
>

Reply via email to