On 10 Aug 2007, at 02:54, Tom Jackson wrote:
I have never been able to put my finger on what the issue is here.
A perfectly viable way of running, I agree; that is not the reason I
would like to see such a module. Let's step into the mind of Joe Newbie:
isn't Apache. Sendmail isn't Qmail either. Both compete over a single
privileged port. That is the real issue. Some company only has one
and needs to make a choice. Then just run AOLserver on an internal
proxy through to it. That is the module. Call AOLserver an
"...hmmm, wat's this thing, AOLserver, let's see. "apt-get install
apache2-mod-aolserver". OK, so no I create a .adp page with some Tcl
code. Cool, but I can do that in PHP too. Ah, I see, I create a
database pool in my .htaccess file and can use it anywhere by name,
neat! And so if I put a procedure in this init.tcl file, it is
available anywhere, without the need for stupid include directives on
every adp page and recompiling the same code over and over again.
Nice. Lets benchmark this thing. Huh? The same code and database
calls run how much faster than my PHP version!?"
I know in the case of debian, AOLserver 4.0.10 is available in
stable, but someone with an "Apache mindset" probably wouldn't find
or try it. Plus the configuration of it would be much closer to
Apache's. (yes, mod-aolserver would probably need to give up the
extreme fine tuning it can do now, but how many people really need
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.