Also if section command be made recursive-aware, so it will track
current position then the syntax can be event more eaiser
section "server/$servername" {
connsperthread 0
flushcontent false
maxconnections 100
maxthreads 10
minthreads 0
threadtimeout 120
section "modules" {
nsdb nsdb.so
nssock nssock.so
}
section "adp" {
map "/*.adp"
enableexpire false
}
section "tcl" {
nsvbuckets 16
library ${homedir}/modules/tcl
lazyloader false
}
section "module/nssock" {
port $port
address $address
}
}
Vlad Seryakov wrote:
> For example instead of this (or it could be used at the same time, it is
> not a replacement)
>
> ns_section "ns/fastpath"
> ns_param cache false
> ns_param cachemaxsize 5120000
> ns_param cachemaxentry 512000
> ns_param mmap false
>
> it may look like this (still Tcl)
>
> section "fastpath" {
> cache false
> cachemaxsize 5120000
> cachemaxentry 512000
> mmap false
> }
>
> section "server/${servername}" {
> connsperthread 0
> flushcontent false
> maxconnections 100
> maxthreads 10
> minthreads 0
> threadtimeout 120
> }
>
>
> As you can see this is Tcl command section
>
> proc section { name args } {
>
> ns_section ns/$name
> foreach { key val } $args {
> ns_param $key $val
> }
> }
>
> But config looks like more 21 century and more structured and easier to
> read. Very similar to lighttpd by the way.
>
>
--
Vlad Seryakov
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
-------------------------------------------------------------------------
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
