Andrzej Jan Taramina wrote:
Antti said:
Actually, I don't, but I still do %-)2. Logger, LogEnabled & Co.I wouldn't include these in the core interfaces. Logger is just another component that could be acquired through the context. This might also help to reduce friction between different projects, as using Avalon wouldn't force them to use a specific logging interface.Absolutely agree.
Imagine that I (admion) have my happy Avalon container running services. Then I get a VeryNiceService and want to add it to my services.
What I would imagine is that I can manage the confifuration and the Logging in the same way as other services... oops, I cannot. I have to learn another logging package. Another configuration system. Blah.
Is this doable with Avalon4... nope ;-)
So, yes, I agree that the current way of doing things can be replaced as you say above. But what I would really like, is a way of managing the above things in a completely uniform manner.
Does this necessarily mean that I need a single logging interface?
Probably not. Put something like JMX in the picture and there is a place for uniform management.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
