This has been a pretty wide ranging discussion, now I'm starting to wonder a little bit, maybe worry a little bit.
There seems to be at least one misconception about the product AOLserver, which should be put to rest: That is about language choice and the ability of introducing new scripting languages into AOLserver. AOLserver is a Tcl application, like Expect. That means that the C code uses Tcl C APIs extensively, for nearly everything. Where the Tcl C APIs fail, they have been supplemented with extensions in C, parts of which have been exposed to the Tcl C and Tcl scripting APIs. Adding another language would be on average more difficult than starting from scratch because you would have to rewrite the entire application, and somehow try to shoehorn the conventions of another language into the AOLserver/Tcl conventions. In addition, most languages were not designed to be used like Tcl for this purpose. However if we could snap our collective fingers and have a multi-language AOLserver tomorrow it would instantly be a huge minus. Because it isn't clear how you would get two scripting languages to work togeather, you would have to choose which one you want to use. You would lose everything written in the other language. The only upside would be that we could have our own little language war right here. tom jackson -- 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.
