> >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. -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
