I think the Configuration interface has a lot of simplicity going for it. I
also think that there could be some additional value provided in some changes to
that interface. But, I'd suggest doing anything like that in a sub-interface.
public interface OtherBitsForConfiguration extends Configuration {
....
}
Gregg
On 1/12/2012 2:04 AM, Simon IJskes - QCG wrote:
On 11-01-12 15:49, Gregg Wonderly wrote:
The deal with ConfigurationFile, of course, is to be able to do
configuration at deployment time, instead of at development time, and
thus, even your development environment is a "deployment" that might be
different from production. For example, in development, you might just
use TCP endpoints, no policy, and a LUS group that is different from the
production environment, so that there is no chance to interfere with
production, which might be on the same routable/multicast-accessible
network.
So in order to keep this scenario in the future, we need to keep the
Configuration interface as the main interface to exchange the configuration
on. Agree?
Gr. Sim
