As part of a popularity drive, why don't we add more stuff to AOLserver? TclLib and tdom in the standard build sound like a good idea. So I believe is my sessions modules. We could merge their documentation into the AOLserver docs, so all is in one place. The same with the Tcl man pages, reformatted to fit in with the rest of the AOLserver docs.
Have a look at the PHP docs and you will see what I mean; everything is in one place. Would it make sense to call AOLserver specific commands that can be replaced with things from standard Tcl or TclLib "deprecated"? (ie: ns_urlget is still there and documented, but we advise people to use the Tcl HTTP package instead) We should also make DB drivers simpler; --with-postgresql and --with-mysql, etc. build options would make sense. Again, include as much as we can in a single download. The goal would be that you can just download and build (or install RPMs or .debs, if someone wants to create and maintain those) and all you need will be there, documented in one place on aolserver.com. That would really lower the barrier to entry by people unfamiliar with Tcl; it will just seem as if Tcl is part of AOLserver itself. Cheers, Bas. -- 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.
