Received: (from majordom@localhost) by hyperreal.com (8.8.5/8.8.5) id BAA19124; Thu, 12 Jun 1997 01:57:55 -0700 (PDT) Received: from gate-isdn.ukweb.com (gate-isdn.ukweb.com [194.152.65.149]) by hyperreal.com (8.8.5/8.8.5) with SMTP id BAA18902 for ; Thu, 12 Jun 1997 01:57:39 -0700 (PDT) Received: from aardvark.ukweb.com [192.168.2.4] by gate-isdn.ukweb.com with smtp (Exim 1.61 #1) id 0wc5jJ-0005GM-00; Thu, 12 Jun 1997 09:59:41 +0100 Date: Thu, 12 Jun 1997 09:57:32 +0100 (BST) From: Paul Sutton To: new-httpd@apache.org Subject: Re: [2.0] proposed vhost config rewrite In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Tue, 10 Jun 1997, Dean Gaudet wrote: > On Tue, 10 Jun 1997, Paul Sutton wrote: > > For example, the every-popular request > > to not log local accesses: > > You can not log local accesses now, just pump your log through a |. > Or post-process it. Why do you want to pay the cpu-penalty and > latency inline with every request? It is a popular request and means we can junk mod_log_referer (which has RefererIgnore). Also if | is used, what happens if the child process dies? Last time I looked (a long time ago) there is no inbuild way for Apache to either notice or to restart it. Maybe it's more reliable now. > I am really concerned that this totally generic language is going to > become one of our worst mistakes ever. Reasons: Yes, it could well be. However it might be better than putting essentially the same code into several modules, which will increase the size of the executable and make maintainence more difficult. At the moment the mod_rewrite, mod_browser and mod_setenvif modules all perform some form of conditional. To add conditional logging into mod_log_config, the same code would have to be added to this module as well. //pcs