httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gonyou, Austin" <aus...@coremetrics.com>
Subject RE: directory_walk performance
Date Mon, 25 Jun 2001 22:03:03 GMT
Sorry to be ignorant, but does directory_walking mean that if no index file
is there, it will display the directory contents instead? If so, am I
correct in noticing that apache2 currently does not allow directory browsing
by default?

-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com 

> -----Original Message-----
> From: Brian Pane [mailto:bpane@pacbell.net]
> Sent: Monday, June 25, 2001 4:09 PM
> To: new-httpd@apache.org
> Subject: Re: directory_walk performance
> 
> 
> William A. Rowe, Jr. wrote:
> [...]
> 
> >On Sat, 23 Jun 2001, dean gaudet wrote:
> >
> >>>that sounds good.
> >>>
> >>>it's just like constant-folding :)
> >>>
> >>>can you generalise it any?  Alias and mod_userdir can add 
> more constant
> >>>factors in the path.
> >>>
> >
> >More complicated than that.  Think rewrite :-)
> >
> >Bill Stoddard and I chatted about this, our collective 
> instinct is that we need
> >to generally cache the intermediate results, and give the 
> operator the choice of
> >how quickly to invalidate it.
> >
> In general, I like this caching strategy.  My approach of pre-merging
> the configs for all constant path matches is applicable on 
> servers that
> have been tuned to disable .htaccess files, but caching of 
> intermediate
> results can yield essentially the same optimization while 
> still supporting
> htaccess.
> 
> The one major concern I have about the caching of intermediate
> results is that the mutex protecting the cache reads/writes will
> become a scalability bottleneck on multiprocessors, but that's
> not an insurmountable problem.
> 
> --Brian
> 
> 

Mime
View raw message