At Friday 10:25 AM 8/26/2005, Tom Jackson wrote:
AOLserver is not in any way similar to Apache, BIND or OpenSSL, other
than
being software.
That's the only similarity I was specifically calling out. Well-designed,
widely-available open source software has converged on a standard way of
handling the build process, and my suggestion is that AOLserver should
follow that path rather than reinventing the wheel. (And beyond that,
that the process should be simplified somewhat for AOLserver 4.)
Apache is a generic system wide service, which a single
instance can assume different environments depending upon the request. It
is
setup by root, but generally useable by everyone.
Yes, and that's precisely how Arena uses AOLserver. Users are running
dozens of separate instances off of the same generic system-wide AOLserver
installation, which is also used for system-level services. It also seems
clear to me that that's how AOLserver is set up to be used, based on the
program options, the config options and methodology, etc, etc...and AOL
seems to agree, since they host www.aol.com with AOLserver.
It's apparent from your postings that you use AOLserver in a different way
than Arena, which is fine. But you also seem to feel that that way is the
*only* right way, and any other way is the wrong way. I don't see any
justification for that belief.
BTW, nothing you've described about your per-user methodology for using
AOLserver is incompatible with Apache in the slightest--you could easily
do the same thing with it as well. Generally speaking, I don't know of
any meaningful way in which AOLserver has to be treated differently from
Apache (beyond the obvious minutiae), and your statement that AOLserver is
not in any way similar to Apache leaves me completely nonplussed.
What is needed is a simple (as simple as possible) tcl script which would
build
AOLserver given a series of answers to relatively simple questions. A
generic
installation would then be the source files and the tcl script. Each user
would run the script for each AOLserver installation.
That would be a nightmare from my perspective, and IMO it would also
restrict the acceptance of AOLserver as a web server platform by new
organizations. But if the build procedure can provide the Tcl script that
you want while not restricting people from doing a standard
configure/make/make install type of build as well, great. Flexibility is
the key.
- John
--
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.
