httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Vary (was Re: cvs commit: apache-2.0 STATUS)
Date Sun, 12 Jul 1998 19:04:27 GMT
FYI, I think this comes "for free" with the work (that I'm finding a hard
time getting to) required to do flow caching of all the fun headers.  Part
of what needs to be calculated to do flow caching of more than just the
simple sites involves calculating vary.  For example, all modules will be
required to "state" what header fields they are using (or could
potentially use) for a particular request. 

Actually it's not quite like that -- what I'm thinking of is something
that happens during config time.  Consider mod_setenvif.  For each per-dir
section it can calculate which headers it will use.  So the core can ask
it "which headers will you use for this per-dir config?" and get a list. 
The core can then calculate the union of all these lists... (and this then
affects how the flow cache will be built for anything that merges in that
per-dir config). 

Note:  this may require changes to some modules, because I refuse to
accept a wildcard in these lists.  If a module can't live without a
wildcard, it will be able to declare that requests can't be flow cached... 

Dean

On 12 Jul 1998 coar@hyperreal.org wrote:

> coar        98/07/12 11:48:20
> 
>   Modified:    .        STATUS
>   Log:
>   	Another issue for future work..
>   
>   Revision  Changes    Path
>   1.40      +4 -0      apache-2.0/STATUS
>   
>   Index: STATUS
>   ===================================================================
>   RCS file: /export/home/cvs/apache-2.0/STATUS,v
>   retrieving revision 1.39
>   retrieving revision 1.40
>   diff -u -r1.39 -r1.40
>   --- STATUS	1998/06/11 10:01:30	1.39
>   +++ STATUS	1998/07/12 18:48:19	1.40
>   @@ -36,6 +36,10 @@
>        If we do this, it needs to be *mandatory* in the style guide.
>    	+1: Ken
>    
>   +  * Really, really comply with 2068 (or whatever Roy says is the right
>   +    document).  Like handling Vary response fields properly and reliably.
>   +       +1: Ken
>   +
>      * Improve mod_include SSI handling, perhaps by caching offsets to
>        directives.  Also, clean up the conditional syntax to allow
>        formats that bear a faint resemblance to other usages (such
>   
>   
>   
> 


Mime
View raw message