I think it would be very difficult to come up with a standard set of
these higher-level features that would please everyone. I'd like to
see lot of extra modules in cvs though.
Yes, in CVS, packaging is another issue but having module sin CVS and be
able to download them from one
place is what i mean.
Very few. Less than we have now? Does anybody use that external db stuff?
Currently we have just nssock which is not module anymore per se, just
an attachement to core http driver
for loading more than once instance which is not always clear. May be we
can teach http driver to bind to as many
addresses without loading different modules.
Then nscgi - usefull, nsco - usefull, nsperm - ???, nsext - ???
Not much to have working server, some DB modules should be there, at
least PG, MySQL, SQLite,
thi is the main selling pitch currentlu for AS, native DB support and DB
pooling but none of the DB modules
included.
I'd like to change the installation layout. Currently it's something like this:
/usr/local/ns/ ...
bin
include
lib
log
man
modules
sample-config.tcl
servers
Can we move "tcl" from modules/ to the top, ussually modules are
empty directory with tcl entry only, do you use modules/ at all?
Also in my installations i use etc/ for all config files, at least i
have nsd.tcl and mime.tcl(with huge list of all mime types)
there plus some other config specific files. Do you think this is usefull?
Here is my structure ( i am not sugesting it, just show what i use):
/usr/local/ns
bin/
lib/
html/
include/
etc/
logs/
tcl/
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
