The main difference to me is that the thread model is not the same. Thread communication in Tcl Threads is done by inserting events into a thread's event queue (or removing events). Similar communication in AOLserver uses a simple queue. Also, all I/O must be non-blocking. I haven't seen an example of how you can do both client/server http requests and database access in the same thread.
So this difference impacts the mapping of AOLserver internals to what is currently available in Tcl. What I have been thinking, which isn't backed up with any real knowledge, is that the nsd binary (stuff that comes from the nsd/ directory) should be modified so that we have something like core modules (like mini-modules) and non-core modules, I'm not sure exactly what the distinction would be, but the point is to create something like a micro-kernel. But what should be in or out, or how this would work, I have no idea. nstclsh is very cool and gives you scheduled procs, logging, and a lot of threading code. I've copied the concept to create an nswish binary, but I don't write Tk code. But it seems that simple servers can be constructed with just nstclsh. If nstclsh could load modules, that would be a huge step forward. Just being able to use the ns_db API within a Tcl app would be cool, then at least my ported web services module would run under nstclsh and have database connectivity. This would allow also nswish Tk applications. Maybe interesting, maybe not. tom jackson On Friday 29 February 2008 09:08, Andrew Piskorski wrote: > On Fri, Feb 29, 2008 at 07:55:28AM -0800, Tom Jackson wrote: > > However, besides the speed difference, AOLserver has many more facilities > > than those available with Tcl. The most important difference is that with > > Well, yes. And it would be very cool to see all or most of > AOLserver's functionality re-factored so that it can be readily > understood and used by OTHER Tcl-friendly applications and libraries. > > If well-done, I also expect that such a re-factoring will help clarify > just what AOLserver has to offer and why it's good. I find it quite > conceivable that stock "AOLserver" could in fact become a particular > configuration of various Tcl-enabled libraries, likely all coordinated > via Tcl's new "ns_config" package... > > And Tom, your email looks like a good start on describing some of the > AOLserver's key generally useful functionality, and why you'd like to > be able to use each part from tclsh. :) -- AOLserver - http://www.aolserver.com/ 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.
