I have addressed the work items below, all changes are in the repository. The 
“keyl*” commands are now deprecated.

Furthermore, i added a section to admin-tuning explaining the spooling threads 
(in essence the driver and writer threads) and worked as well through the other 
sections, removed some SGI stuff, etc.
https://naviserver.sourceforge.io/5.0/manual/files/admin-tuning.html

Altogether, we have 90 commands/subcommands deprecated. I am still planning for 
the release to add an option to build NaviServer without the deprecated 
commands (default is with deprecated commands). Why should every NaviServer 
binary carry these around? Esp. for constraint environments, this is not 
desired.

All the best
-g

> The statistics refer just to the commands starting with “ns” to leave out 
> some of the internals, which are not too many.
> We have 6 C implemented commands not starting with the usual NaviServer 
> prefix, and one command which was intentionally not documented:
> 
> - I will document “ns_crash”, If no one objects.
> 
> - the keyl* commands are inherited from TclX. From my point of view, there is 
> little reason to use in new programs, since it resembles in essence the Tcl 
> “dict” functionality with a different syntax.
>    (correct me, if I'm wrong am wrong). 
> 
>    I see the following options
>     * deprecate it 
>     * put it into a separate module
>     * drop it, since tclx is still maintained by flightaware 
> (https://github.com/flightaware/tclx/), so people can load it via “package 
> require”.
> 
>   I am in favor of deprecating it in NaviServer 5, such that users get warned 
> about its usage.
> 
>  - _ns_adp_include: In my understanding, the only reason for having a command 
> “ns_adp_include” and a separate command “_ns_adp_include” is the proc 
> call-frame on the top-level to keep local variables. It should be possible to 
> create this call-frame via the public API of Tcl.  I will look into this. 
> 
> As always, feedback is welcome.
> 
> -g

_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Reply via email to