On Dec 4, 2007, at 5:23 PM, Vlad Seryakov wrote: > nsd.tcl is still the only place for config, it is just instead of > hardcoding registration of callbacks for ADP in c, now they are > registered in Tcl. That means, without config.tcl .adp files will > not be > served even if enabled in nsd.tcl.
Bingo. Exactly this happened here. > > > I am not sure if this is good moving core functionality into Tcl, that > means running just nsd binary now will not work properly without > proper > tcl/*.tcl files Hm... I believe there pros/cons for both. At the moment I see only cons but this might change after thinking awhile. The problem now is that config for the ADP module is dependent on two places. The config file (ns_section/ns_param) and some other magic (config.tcl) that runs ns_register_adp. If we'd follow the "module" logic and encapulate all that module needs to do in the module directory (of course we need to declare a ADP module!) then it would be logical. You would have a "module loader" that is Tcl and module can have whatever it likes (only Tcl, C or a mixture of files). But as is now, it is very confusing. At the moment I'm in a great stress to roll-out our V3 beta release so I cannot think much about that (packaging). I just need to make it work again. But I will think about that soon. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
