David Hodgkinson ([EMAIL PROTECTED]) said something to this effect:
> Hmmm...what about a variant of the proxied mod_perl?
>
> Picture a lite bulk front-end apache doing the usual stuff then
> proxying the mod_perl stuff back to a serverly (chargeably?)
> process-limited apache with a different httpd.conf per site?
We are using a decent solution to handle hosting for employees personal
domains, although it is on a pretty small scale:
A single public address, with all the names pointing to this address. It has
mod_proxy and mod_rewrite enabled (and very little else) and each VirtualHost
section is merely a ProxyPass directive.
The actual domains themselves are running on dedicated high ports on virtual
addresses attached eth0 (eth0:1 is bound to 192.168.0.1, eth0:2 is bound to
192.168.0.2, etc). The VirtualHost directives look like, sometimes with a
ServerAlias directive, but never more than that:
<VirtualHost 12.34.56.78:80>
ServerName www.foobar.com
ProxyPass / http://192.168.0.2:8000/
</VirtualHost>
And each server (running on dedicated private addresses, on high ports so
that the user can start and stop the server without root access) maintains
its own configs and setup. We get a bunch of traffic, with 6 hosted domains,
and about 45 httpd processes. The server is a Penguin Computer box (plug!
plug!) with a PIII-500 and 128 Megs of RAM; a decent box, but not a huge
one.
darren
--
Kill Ugly Radio
