Nobody can argue that better isn't better. There are certain things which seem 
difficult in AOLserver, maybe more difficult than they should be, but maybe 

One is writing a new C module. I've done some where I use a shared .so module 
for the interesting library code, and I think I have used a static .la (or 
whatever it is) file.  The difficulty seems to be in using the Tcl C API to 
make a place to store application data, like handle pointers, etc. Maybe this 
is just as hard in Apache? Being able to more easily reuse existing C 
libraries would provide a long term benefit. Maybe this would be easier with 
ns_proxy and a single threaded/isolated process. 

Another issue related to C modules is that you can load libnsd into a tcl 
interp, or just run nstclsh. But you can't load modules, or at least I don't 
know how to do it. It would probably take a lot of work to get nsd to run as 
a server inside a tclsh, but what about being able to run nsd with no 
servers, maybe with Tk as the face of the process, maybe a new main function 
called nstk. Seems complicated to do,  maybe just a module needs to be 
written that could startup a Tk thread? Being able to use the database and 
scheduling APIs in a desktop application would be an intesting new area for 
the AOLserver codebase. Maybe there is something already in this area with 

tom jackson

On Thursday 09 August 2007 11:28, Daniël Mantione wrote:
> Besides this, AOLserver needs to get better in replacing Apache as the
> primary web server on a system, and this means getting multi-user
> capabilities itself. Depending on the way it is done, it can be low
> hanging fruit too.

AOLserver -

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to