According to Soulhuntre:
> > My favorite is throwing a proxy in front...
>
> The issue in question was getting the perl core out of the address space of
> the httpd process entirely :)
>
> Velocigen does this nicely (though there is a performance penalty) and even
> allows degicated machines runnign the perl services that talk to the
> webserver over sockets.
Look at the problem from the opposite direction. There is not
that much overhead in including http in the perl processes
actually doing the work, and (unsurprisingly...) http turns
out to be a reasonable protocol to forward http requests
instead of inventing something else. So, consider mod_perl
to be the backend perl process with a non-mod_perl frontend
using ProxyPass and/or RewriteRules to talk to it amd
you end up with the same thing, except more flexible, with
a single config file style, and the ability to test the backend
with only a browser.
Les Mikesell
[EMAIL PROTECTED]
