I have one more proposition to make:
In case of multiple servers sometimes it it is easier to maintain and
provision when config files are stored locally. I used to have server
software that load config file on startup over HTTP and i would see that
a usefull feature for naviserver as well. Image that you start it as
nsd -t http://server:80/nsd.tcl
and it will get the config file from the central server that will
provide what is necessary, even on-the fly generating some config
parameters. We have HTTP facility in the core, so it is easy to call it
to retrieve the config and continue as usual.
Of course there is a posibility that it will not be able to connect and
thus will not be able to run but this can be handled by keeping last
copy of config and load it in case of network issues.
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
