On Sun, 7 Oct 2001 17:22, Mircea Toma wrote: > The way I see the configuration serializer has nothing to do with this > 'Notifier'. The ConfigurationNotifier is a helper class for the > ConfigurationRepository (sort of BlockListenerSupport) to > notify/reconfigure registered components. To answer your question, the > Application will register a block with a certain configuration from > repository. The configuration stored in ConfigurationRepository is updated > at its turn by a different process like a FileMonitor or directly by the > SystemManager. A configuration serializer would be used for the opposite > direction when the configuration stored in ConfigurationRepository is > modified the (cloned) file will be updated by a listener.
Oh - ok. I still think a new Listener should be used for this. The reason is that we can't directly call reconfigure() on the block. What we have to do is signal the kernel that Block X needs reconfiguring. The kernel may have to stop stop other Blocks that depend on block that is getting changed. Then it grabs the Block and calls stop(), reconfigure() and then start() again if all goes well. I am not sure. We haven't really decided how we are going to handle re* methods yet as it brings up a lot of concurrency issues. I dunno ;) -- Cheers, Pete -------------------------------- These aren't the droids you're looking for. Move along. -------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
