Gleaning from this conversation a few main points/questions, with a couple cents of my own thrown in:
1) AOLserver probably needs a new name. Something that uses the NS initials would be ideal so that all those ns_* commands actually make sense again. Could we resurrect the NaviServer name? 2) The biggest bang for our buck would be improving the Tcl language and the codebase available for it rather than bringing in another popular language. It took Rails to put Ruby on the map. What would our Rails be? 3) What other features does AOLserver lack that would tap into current trends, or possibly create future ones? Server-side JS is interesting, "Comet" support seems like a good candidate? 4) Who could sponsor AOLserver development apart from AOL? Does anyone know of anyone with a large deployment of AOLserver? 5) Which will come first, Tcl gaining in popularity or AOLserver, or do they both need to grow together? 6) If AOLserver remains a targeted product, as it seems right now it should, it's usefulness will be limited by what can run on it, and what can integrate well with it. Which is fine, but we need to have that clear in our minds as we proceed. I don't think we want to topple Apache per se. We want AOLserver to carve out its own path, and if along the way it makes Apache, etc. irrelevant then great! -Titi -- 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.
