On Tue, 21 Aug 2001, Mircea Toma wrote: > > ----- Original Message ----- > From: "Berin Loritsch" <[EMAIL PROTECTED]> > To: "Avalon Development" <[email protected]> > Sent: Tuesday, August 21, 2001 11:50 AM > Subject: Re: LogKitManagement > > > > Mircea Toma wrote: > > > > > > Hi, > > > > > > I thought that the purpose of LogKitManagement was to avoid the circular > > > depedencies Avalon<->LogKit. If you still use Configurable, > Loggable..... > > > why not use a ComponentManager/Selector to do the same job? > > > > Because it is the wrong pattern. We don't obtain loggers by > > selecting them (how would we know if we couldn't select the right > > one). > > > > Yes, but targets/categories can be selected isn't it (assuming there is only > one hierarchy)? > > > Also, this is avoiding the dependency of LogKit requiring Excalibur. > > If you have dependencies only going in one direction, then you can't > > have circular dependancies. > > > > LogKitManagement will live in Excalibur, and use Excalibur tools > > and Framework tools. LogKit is completely unaffected by the LogKit > > Management framework. In fact, all the LogTargetFactories that are > > Configurable live in Excalibur with the management framework. > > Ok, I thought it will be part of LogKit :)
No, definitely not. It's part of Excalibur. Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
