Ryan Bloom wrote: > > > > I'm in favour of a mechanism that doesn't require every single > > > generated-content module to be rewritten to include an essentially > > > duplicate function. > > I'm in favor of doing this in the code and not forcing every > administrator to reconfigure their server to get this functionality.
For modules in our bundle, by all means do them right -- as long as it doesn't mean writing an essentially identical map handler for each. If we need to do that, then something's wrong. However, I think we should provide something to allow 3P module usage to avoid the stats without requiring that *they* be rewritten. > Understand that introducing the DocumentRoot directive inside a > <Location> container doesn't remove the stats automatically, it > requires that every admin change their mod_status config to: > > <Location /server-status> > DocumentRoot unset > SetHandler server-status > </Location> For 3P modules I think this is acceptable. If a webmaster cares about the performance, let him do it. If he doesn't, he's no worse off than in 1.3, where he couldn't do anything about it anyway. > If the module is implemented correctly it can handle this. But some 3P modules will NOT be more than minimally tweaked to run with 2.0. I think providing a means for the sysadm to save them from stats is goodness; it puts the sysadm in charge of performance tweakability, rather than putting him solely at the mercy of (potentially unaware) module writers. And if the sysadm is unaware, again, he's no worse off than before. This just gives him a chance to be *better* off than before, if he knows and wants it. -- #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!"
