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 -- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
