From: "Roy T. Fielding" <[EMAIL PROTECTED]> Sent: Friday, October 05, 2001 8:42 PM
> On Fri, Oct 05, 2001 at 04:06:56PM -0700, Ian Holsman wrote: > > hey guys. > > > > just got a simple question. > > > > What would the ramifications be if we changed the config options from > > 'directory specific' to 'server' specific. Huh? How do you mean? Which options? > > I mean what functionality would we lose if we were just able to set all this > > options once (server wide) Well you would break any module you did that to. You loose the ability to set it on Location, by Files, or by any other non-vhost container. And you need to change the server to look up by the sconf instead of the dconf. > > The reason I'm asking is that in CNET's case (and probably other corporate > > web-sites) > > most of these things would be set only once, and all the merges are just a > > waste of CPU. Not anymore ;) That is, we might have a few merges, but they are an order of magnitude faster on subrequests and redirects. And realize that merging two <Directory > (or other such) blocks, where a module has no per-section directives, means that it simply references the one that does exist. Therefore, you don't really merge when you place all directives at a global or vhost scope. If a <Directory > block contains only a single LanguagePreference directive, it merges only core and mod_mime per-dir-configs. > Are the merges still being done when AllowOverride is false? That is the > config directive to use in this situation. Uhhh... no, merges still occur. We merge <Directory >, <Files > and <Location > blocks always. We just skip read/parse/merge of any htaccess file. Bill
