Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com
 designates 209.85.160.171 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Next Log4j 2.0 release
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: <866984883500894999@unknownmsgid>
Date: Wed, 2 Jan 2013 07:35:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F268A0C0-F55B-4A78-B32B-84C6A9DEE075@dslextreme.com>
References: <B89F162D-B463-4A76-8281-81CC1648C517@dslextreme.com>
 <866984883500894999@unknownmsgid>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>


On Jan 2, 2013, at 4:50 AM, Gary Gregory wrote:

> On Jan 1, 2013, at 14:37, Ralph Goers <ralph.goers@dslextreme.com> =
wrote:
>=20
>> I took me longer than I wanted but I have finally fixed all the =
issues I wanted to complete before doing the 2.0-beta4 release.  Please =
let me know if you are aware of something else that needs to be done =
before the release.
>>=20
>> A larger question is whether the subsequent release should be beta5 =
or whether we are good to go with the 2.0 GA release.
>=20
> For beta 5, I'd like to add a JDBC appender. We use one at work for
> certain set ups. Alternatively, can flume to set up to log to a
> database?
>=20

Flume is basically an event bus.  If you have a setup with web, =
application and data tiers and you don't want your web tier to have a =
jdbc connection to the data tier then you could use Flume to send the =
events to the application tier to be written.  Flume also acts as an =
aggregator so that if you have 10 instances they can all write to Flume =
where you then only have a single connection to the data repository.

I'm not a huge fan of using a relational database as the repository for =
logging events but if a DBAppender is needed then lets add it.

Ralph=20


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org