Op Tue, 7 Aug 2007, schreef Dossy Shiobara:

> Hold on a second--define "superior," please.  I see absolutely no reason
> to run a separate nsd process per user, giving you full process
> isolation instead of this uid-juggling stuff that Apache does.  With
> Apache, if you want to make a server config change, you have to bounce
> the whole process which affects all users.  If you run a separate nsd
> per user, each individual user is isolated from each other
> completely--including server restarts.
> If they all need to share the same IP/port, sit a reverse proxy (Pound,
> Squid, Perlbal, etc.) on that port and have it proxy requests to the
> appropriate nsd bound to its own separate port.  Sure, there's going to
> be some overhead (the proxy) but it gives you the ultimate in
> flexibility--especially if the proxy can be reconfigured at runtime
> without a restart.

Ok, practical example:

We have a server, two users want to run OpenACS, and 20 users simply 
wants to code PHP/MySQL. Proposal to the system administrator: Put pound 
on Port 80 and have requests for the two OpenACS users redirected to their 
own AOLserver process.

Now, everyone on the server will see all requests coming from localhost. 
Big chance is the PHP/MySQL users won't like that and put the argument
"just use what everyone else uses" in place against the OpenACS users.
> The net here is that AOLserver really isn't designed to be used by
> commodity web resellers who host thousands of tiny sites on a single
> box.

Commodity resellers are an extreme example of a multi-user environment. 
There are many web servers in use that have a much smaller amount of 
users, like a company that has a webserver where some its developers 
can develop in their own "user web" space, students that run a web server 
together on their campus internet connection, etc.

Note that it's suitability for multi-user environments is the single 
reason why Apache did beat IIS. It is the reason Linux is so dominant in 
web serving.

> For non-trivial web applications, you're already going to need to
> have some reasonably complex web infrastructure (load balancers, caching
> proxies and CDNs, etc.) in place--and as a cog in that larger machinery,
> AOLserver certainly solves a set of problems nicely.



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.

Reply via email to