> -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > Sent: den 12 september 2001 14:57 > To: Avalon Development > Subject: Re: Configuration management > > > Peter Donald wrote: > > > > On Wed, 12 Sep 2001 09:02, Mircea Toma wrote: > > > Hi, > > > > > > To change the Configuration at runtime we need a > ModifiableConfiguration (I > > > know that there were some discussions about this) in this way > I can have > > > the management written against a interface not a class. I guess the > > > interface is straight forward since this functionality is > implemented by > > > the > > > DefaultConfiguration: > > > > Sounds good to me.
I am against it. I think it is more about when it can be written to than who does the writing. The ComponentManager should deal with this by re-initializing components with static, read-only configurations when they are returned. So for the three types of components: Recyclable: Instead of recycling, see if the component is reconfigurable and reconfigure it. Otherwise, dispose and re-initialize. Threadsafe: Wait until all references are released, re-initialize. Single-threaded: Switch. Otherwise we will have race conditions all over the place. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
