Re: cvs commit: httpd-2.0/modules/experimental mod_cache.c

[Justin Erenkrantz]

On Mon, Sep 03, 2001 at 06:30:54PM +0200, Graham Leggett wrote:
> I think that the cache should store data *without* transfer encodings
> applied: Ie not chunked and not byteranged. This solves your problem.

I'll jump in here now that I have an idea what you are talking 
about.  I think our filter classifications can be:

handler--->content-filter->cache-filter->transfer-filter->network
(default)  (mod_include,   (mod_cache)   (mod_gz{ip},     (core)
            mod_php)           ^          mod_proxy,
                               |          byte ranges)
                         can short-cut 
                  handler and content-filters

Multiple filters in the chain for each classification can exist
(ordering between classifications shouldn't matter...)  This
way you can have a URL handled by mod_include and mod_php (but
the mod_include portion can't create PHP tags and vice versa
since you can't guarantee when it will run in relation to the
other).

I have no clue how this relates to our code or how others sees
this.  This is my quick uninformed birds-eye view.  Thoughts? 
This ordering seems to be a problem that we need to address.  
-- justin