Shane Nay <[EMAIL PROTECTED]> writes:
> > 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?
> >
> > Nah, not good, you still have to budget a fair few meg per mod_perl
> > site.
> >
> Yea, that's the problem as I see it..., modperl processes can be
> _huge_, so you need a finite way to control with an absolute hand
> the size of those processes.
Limiting by number of threads on that users own dinky little apache
seemed a plausible way to go. At least apache and mod_perl are
shared. But every user will end up with a CGI.pm or somesuch in this
scenario.
Plus, I've fixated on Apache::Registry type stuff, not dinky little
per-site bits of code.
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Highway Star http://www.deep-purple.com
Apache, mod_perl, MySQL, Sybase hired gun for, well, hire
-----------------------------------------------------------------
