You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Chad LaVigne <ch...@yahoo.com> on 2008/09/05 21:49:53 UTC
Fw: Burst filter
I sent this message regarding a code contribution a little over a week ago and haven't received any feedback.� Is this still the correct mailing list for contributions?
--- On Mon, 8/25/08, Chad LaVigne <ch...@yahoo.com> wrote:
From: Chad LaVigne <ch...@yahoo.com>
Subject: Burst filter
To: log4j-dev@logging.apache.org
Date: Monday, August 25, 2008, 8:59 PM
A long while back I submitted a code contribution to be considered for log4j 1.2.� It's a filter to regulate logging traffic bursts.� It's useful for situations where you may want to limit the number of logging messages that are sent to an appender, i.e. when the database goes down you don't want 2 million e-mail logs taking out the mail server.� I received a response requesting I change the name to something like BurstFilter, a good suggestion indeed.� Sadly it's taken me a year to get around to this but I finally have.� It looks like no further development is planned for 1.2 except for bug fixes and minor enhancements.� Is this feature small enough to be considered a minor enhancement or should I submit the filter for 2.0?
Thanks,
Chad
Re: Burst filter
Posted by Chad LaVigne <ch...@yahoo.com>.
I submitted this code contribution to bugzilla as item 45753.� Does anyone have any feedback on it?
Thanks,
Chad
--- On Fri, 9/5/08, Curt Arnold <ca...@apache.org> wrote:
From: Curt Arnold <ca...@apache.org>
Subject: Re: Burst filter
To: "Log4J Developers List" <lo...@logging.apache.org>
Date: Friday, September 5, 2008, 5:07 PM
On Sep 5, 2008, at 2:49 PM, Chad LaVigne wrote:
> I sent this message regarding a code contribution a little over a
> week ago and haven't received any feedback. Is this still the
> correct mailing list for contributions?
>
Yes, but entering it in Bugzilla (http://issues.apache.org/bugzilla)
is preferred. Many mailing list archives do not retain the
attachments, so an Bugzilla entry from you with the source code
attached has a better audit trail. You do have to first create the
issue and then subsequently make the attachments.
As for feedback, the previous weekend was a holiday in the US which
may explain why your contribution didn't get much attention.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Burst filter
Posted by Chad LaVigne <ch...@yahoo.com>.
Thanks for the advice Curt.� I made a Bugzilla entry.� I attached the source as a zip file, I hope that works.
--- On Fri, 9/5/08, Curt Arnold <ca...@apache.org> wrote:
From: Curt Arnold <ca...@apache.org>
Subject: Re: Burst filter
To: "Log4J Developers List" <lo...@logging.apache.org>
Date: Friday, September 5, 2008, 5:07 PM
On Sep 5, 2008, at 2:49 PM, Chad LaVigne wrote:
> I sent this message regarding a code contribution a little over a
> week ago and haven't received any feedback. Is this still the
> correct mailing list for contributions?
>
Yes, but entering it in Bugzilla (http://issues.apache.org/bugzilla)
is preferred. Many mailing list archives do not retain the
attachments, so an Bugzilla entry from you with the source code
attached has a better audit trail. You do have to first create the
issue and then subsequently make the attachments.
As for feedback, the previous weekend was a holiday in the US which
may explain why your contribution didn't get much attention.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Burst filter
Posted by Curt Arnold <ca...@apache.org>.
On Sep 5, 2008, at 2:49 PM, Chad LaVigne wrote:
> I sent this message regarding a code contribution a little over a
> week ago and haven't received any feedback. Is this still the
> correct mailing list for contributions?
>
Yes, but entering it in Bugzilla (http://issues.apache.org/bugzilla)
is preferred. Many mailing list archives do not retain the
attachments, so an Bugzilla entry from you with the source code
attached has a better audit trail. You do have to first create the
issue and then subsequently make the attachments.
As for feedback, the previous weekend was a holiday in the US which
may explain why your contribution didn't get much attention.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org