> Another change I was considering but are not sure about is making each
> Logger only have 1 LogTarget. It originally had multiple
> logtargets because
> I was in a servlet environment and needed to sometimes log to servlet log
> and sometimes to a custom log.
> This would make it faster for single logtarget case but a bit slower for
> multiple logtargets. Question is what pattern is more common? Multi or
> single? Thoughts?
I think multiple.
1) The most common case is that you want to store the log
messages in some kind of repository (ie textfile), AND notify the sys admin
in case of problems needing immediate attention.
2) I imagine an avalon installation running many sars. For each sar,
warnings and errors are logged separately. But it seems likely you'd
also want errors from one sar that may affect another (which will
probably happen somewhere) logged in an avalon log file.
3) not to mention complicated distributen multi-server envs - which
usually need the speed.
MORE ON LOGGING
---------------
I believe I said I would be looking into logging stuff, and I'm on that
at the moment. There's only one big issue:
jakarta's got both Log4J and Avalon's LogKit.
I believe it is important to decide _now_ how to resolve this. Options:
1 - merge logkit into log4j.
2 - make logkit wrap around log4j (so log4j can be used in 3.1~ avalon).
3 - in avalon 4 (or whatever it should be called), remove logkit in
favor of log4j.
4 - don't resolve; keep the separation forever.
2 & 3 could both be done, but that'd be imo, a waste of time.
I think option 3 is the best (based on my reading of e-mail archives).
However, there might be advantages to logkit that log4j doesn't have.
Could someone (Peter ;-) enlighten me here?
I'll create a detailed proposal when I have the full picture =)
greetz,
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
