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