Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3A1C6E6F.9090804@olliance.com>
Date: Wed, 22 Nov 2000 17:10:07 -0800
From: Jason Brittain <jason@olliance.com>
Organization: Olliance Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-12 i686; en-US;
 m18) Gecko/20001107 Netscape6/6.0
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: [PROPOSAL] Tomcat 4.0 Milestone 5
References: <3A1C4249.8F7A575D@eng.sun.com> <3A1C6487.4060304@olliance.com>
 <008301c054e7$9ffd4c90$82deb018@intalio.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Remy Maucherat wrote:

>> Just so you know, I've been looking at the AccessLogValve,
>> and am working on getting it into shape to be re-enabled
>> in the default config.  In the process, I'm writing a Valve
>> tester so we can test and benchmark Valves.  It's already
>> running, but it's not quite ready for release yet..
> 
> 
> I would like that by default it doesn't do any kind of pattern matching at
> all (unless one is explicitely specified), and just output the standard log.


You're talking about the AccessLogValve itself, right?  You want an
AccessLogValve that doesn't do any fancy pattern stuff, but built only
to do the common log format?  Yes, that would sure help it to perform,
wouldn't it?  And, we could have another Valve that does the fancy log
patterns of people want that feature.

-- 
Jason Brittain
Software Engineer, Olliance Inc.        http://www.Olliance.com
Current Maintainer, Locomotive Project  http://www.Locomotive.org