Bill Stoddard wrote:
> 
> > However, I think we should provide something to allow 3P
> > module usage to avoid the stats without requiring that
> > *they* be rewritten.
> 
> I disagree with the last sentence.  We should not complicate
> the configuration of the server more than it already is to
> accomodate poorly written Apache 2.0 modules.

Um, what complication?  Nothing gets added to the config by
default, but it would provide a way for the sysadm to work
around performance hoggishness -- IF he wanted to do so.
Without something like this, he's just plain stuck.

> Module authors are a small group and they can learn to do
> the right thing.

Huh.  Let me try a couple of names on you: FrontPage. ColdFusion.
Do you think they're ever going to do the right thing, even though
they have a significant penetration?  Many modules are written
by individual, but quite a few are written by corporate entities --
who aren't likely to be the least bit interested in spending any
more time on their modules than that needed to get them working
(just) on 2.0.

> Apache 2.0 users are a -much- larger group and we should be
> more mindful of making changes that adversely affect the users.

Please explain how a non-default change that could improve the
server's performance -- IFF the sysadm makes it -- adversely
affects the users?

Why did we make 'HostnameLookups Off' the default?  To improve
performance in the default case.  Why won't we add a knob that
will let the sysadm reduce stat() calls?  I don't know, please
tell me..
-- 
#ken    P-)}

Ken Coar, Sanagendamgagwedweinini  http://Golux.Com/coar/
Author, developer, opinionist      http://Apache-Server.Com/

"All right everyone!  Step away from the glowing hamburger!"

Reply via email to