Noel J. Bergman wrote:
From a user's prespective, whatever path would allow Merin to provide properlogging removes a barrier to adopting it as a standard container. The cleaner proposal is a good one, but is what is the difference in delivery time?
I'm digging into Excalibur Logger as we speak. I remember doing this way back and I'm now starting to remember all of the reasons why I don't leverage Excalibur Logger at the time. What it comes down to is a few problems:
(a) as Berin mentioned - lots of legacy cruft to sift thought
(b) is too tightly linked with LogKit in its current form
(c) does not seperate easily named targets establishment from parameterized channel establishment
On item (a) a version 2.0 could clear this away.
On item (b) a new set of SPI interfaces could resolve this + refactoring of implementations
On item (c) means proper thinking and upgrades across multiple implemetations
Which all suggests a lot of time - which brings us back to the "use as is" scenario - but this is problamatic because Merlin needs seperation of target creation from channel creation.
I.e I don't know yet.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
