Hi Vlad, I like the idea but I would abstain from voting, because I think I personally would write a shellscript for it and make use of "wget" or "curl". Those tools offer tons of options, e.g. - http, https, ftp (active/passive mode) support - certificates, passwords; http digest authentication - http proxy support - tls, ssl - different retry and timeout parameters - server response can be logged etc. So this would not have to be maintained in the core. You need some logic anyway that deals with failed connections, so this is - in my opinion - the part of the startup script.
BTW, such a script could be placed into the contrib section (Would be nice anyway to have examples for different distros, I will soon add one for SuSE) No vote against it from me, but I would implement it with external tools. > 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.
