logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject RE: Task Priorities
Date Mon, 09 Sep 2002 22:23:05 GMT
At 15:11 09.09.2002 -0700, you wrote:
> > >1) Define/investigate plugin design (as suggested by Nicko
> > Cadell).  The
> > >idea is to setup up a general mechanism to allow extensions to the
> > >architecture; at least the parts that live at the
> > LoggerRepository level.
> > >Both the Receiver and Watchdog proposals could use this mechanism.
> >
> > The coupling suggested by Nicko Cadell seems correct to me.
> > Extensions
> > should know about the LoggerRepository but not the other way around.
>I think something still needs to know about the "plugin" so that they can be
>found/stopped/etc, but that knowledge does not need to be attached to the
>LoggerRepository.  Something like a PluginRepository, PluginManager, or some
>such class.




TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793

To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

View raw message