On 24.10.2007, at 23:41, Stephen Deasey wrote: > The basic idea of a callback seem to fit fairly naturaly to how the > code currently works. And I like the idea more than a hard dependency > on some DBM library. > > I also like the idea that it serves two functions: it's a hook which > can be used to dump config, but it can also be used to handle updates > to systems with different locking schemes than atomic key/value pairs.
I see... So one would register a callback into the config module to "monitor" the params change instead of doing it all the time explicitly. Good idea. This is worth the effort. I will add this. What I did not get is "hook which can be used to dump config" As we do have introspection built in, why do I need callbacks for that? I'd just simply walk all sections and params in a Tcl script and dump them all in a ns_section/ns_param format (loosing comments, allright). ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
