t isn't an architectural
feature change so I wouldn't have any problems with it going into 3.2.x,
just not right now.
> -Original Message-
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 23, 2001 6:41 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Access log fi
80E6
>-Original Message-
>From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 23, 2001 12:44 PM
>To: '[EMAIL PROTECTED]'
>Subject: RE: Access log files in the style of Apache
>
>
>Hola a Todos, Costin, Jochen:
>
>>
>> +1 for
Hola a Todos, Costin, Jochen:
>
> +1 for 3.3,
> +1 for checking the code in for 3.2 ( but not enable it be
> default ) - it
> can't hurt in any way code stability. ( but it's Marc's call )
>
+1 to add it to 3.3 release
+1 and to provide it disabled for upcoming 3.2.3, if MArc agrees..
S
Quoting [EMAIL PROTECTED]:
> Please send the source file - you attached a .class :-)
So sorry - here it is. :-)
Thank you,
Jochen
package org.apache.tomcat.logging;
import org.apache.tomcat.core.BaseInterceptor;
import org.apache.tomcat.core.ContextManager;
import org.apache.tomcat.core.R
Hi Jochen,
Thank you for this patch - it is something very needed. I don't think this
can make it for 3.2.2 release ( but it can be made available for people to
compile as a separate module), but it'll be available for 3.3 ( I hope
in the default distribution - but we do have the option of makin
