On Wed, 2008-05-14 at 13:38 -0700, Kevin Thorley wrote: > At the current time, I do not see the need to have support for custom > parameters that are different on different hosts. I feel that this will > be a large amount of work and I haven't seen a use case to justify it. > However, neither do I want to stand in the way of other developers that > want to use sipXconfig, but also have the ability to manually change > config files. So, my suggestion is to include a switch in > sipxconfig.properties to fully disable the new config file replication. > If this replication is disabled, then all config files will need to be > created by hand and manually copied to distributed systems. Will this > solution fit the current problem?
I don't see how that differs from just not running sipXconfig at all (which requires no switch) -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
