Daniël Mantione wrote:
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.
Lots of proxies support adding in additional http headers to indicate
that it is a proxied request. In certain environments (firewalled
corporate paranoia) you can't avoid everything being proxied and must
deal with this. And more to the point, there are simple ways (about 4
lines of code in a PerlFixupHandler) to recover the proxied connection
address from such an added-in header if people are really upset about it.
Or as an alternate answer: use apache itself as the proxy. The poor
saps who subject themselves to PHP will be happy and the OACS users can
have a real system to work with.
Obnoxious alternate answer 2: tell the php users, "sorry, there's people
doing real work on this system." :)
Bottom line is, there's no reason why they can't coexist peacefully.
-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.
