Re: [configuration] ConfigurationFactory & namespacesI agree with everything excelpt the last one, merging the two.. CompositeConfiguration is a very simple holder for configurations. You can easily use it programatically for example.
Even if CompositeConfiguration had a persistence mechanism we could still use it programatically independently of any configuration file. I'm not convinced this is a good idea yet, I just wanted to throw it there and discuss it.
However, ConfigurationFactory brings a lot more with it.. Including with what you propose the ability to reload itself.. Something to think about is that if ConfigurationFactory is going to start reloading itself, then maybe we need to think about how we are going to bolt in out event handling stuff.
I haven't really started studying the event handling yet. What are the needs ? Notify about properties added, changed or removed ? Notify about configurations reloaded ? Should we trigger a single event with a list of all the properties modified, or an event per property changed ? The design choices of the [event] component in the sandbox might help us in implementing this feature.
On a related note, now that Vector has been removed, and you have tossed in a bunch of small features and stuff that had been sitting around. Should we think about a 1.1 release? I know, it seems soon, but... Release early/release often...
Hmmm once I land INIConfiguration why not.
Emmanuel Bourg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
