I was referred to this mailing list from the following thread on perlmonks
(http://www.perlmonks.org/index.pl?node_id=693487)
===
For years I have been using modperl and have been quite fond of it, the idea of
persistant perl interpereter is excellent.The probl
On Mon, Jun 23, 2008 at 8:46 PM, James Austin <[EMAIL PROTECTED]> wrote:
> 1) Requires a new http server for each additional site/modperl application
> 2) Apache creates a set of workers for each instance (ususally about 7).
> With 7 required for the Top level proxy, and 7 for each site, this soon
James Austin wrote:
Advantages:
1) Provides persistant perl WITH suexec for per-virtualhost user
execution
2) SpeedyCGI handles dynamic data, Apache handles static, hence you
don't require a covering proxy as described in
http://perl.apache.org/docs/1.0/guide/strategy.html
