Daniël Mantione wrote:
I think this may be more of a marketing issue than a technical one. What does
apache do that aolserver doesn't?
If have had very few situations that could rely 100% on AOLserver. Be it
PHP scripts (yes, I know you can install PHP in AOLserver), multi-user
requirements or political issues.
>
There is no major technical issue with AOLserver. Not at all. The devil is
in the details. There are social issues at work (of which some might be
addressable with minor technical interventions).
We are in agreement here.
This is really the heart of it - it is a social and/or political issue,
not a technical one that leads to the poor interoperability. Which is
exactly what I said - its a marketing issue.
Maybe we (the community) could do the legwork for those technical
interventions to address some of those social concerns. Item #1 for
such interventions I think would be a apache -> aolserver migration
guide, not aimed so much at moving a configuration from apache to
aolserver (although that would be useful too) as helping an admin who
has configured apache previously configure aolserver.
the only problem is if they want to do things as
themself rather than as the aolserver uid, since AFAIK setuid and threads do
not interact well.
... and there is one TCL library, all databases need to be configured
globally, cgi scripts cannot be run with user permissions and more. For
multi-user systems, Apache is superior.
Admittedly its been a long time since I've worked in a highly multi-user
environment, but I think these points mostly apply to running external
CGI programs, and once you're execing an external progrqam it doesn't
matter too much what webserver you're running. For in-process stuff (at
least with mod_perl) apache suffers all these same problems, in many
cases to a far greater extent.
Yes, this is one of the solutions. It can technically be done, in multiple
ways, it is even doable, but that is not the point. There is competition
on port 80, and you need to have a good story to convince your sysadmin
(or find concensus in your open source project) to replace Apache with
AOLserver on port 80. Again, a social issue.
Again, a marketing problem. It comes down to "no one is using it
because no one is using it."
Idle curiosity - I wonder if anyone is running a system with both apache
and aolserver listening on port 80 on different ifs/ips. Should be
possible and not even difficult, tho probably of limited utility.
-J
--
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.
