|Problems? Is your data what you think it is?|
Re^2: Perl/FastCGI - What happens on exit?by afoken (Monsignor)
|on Nov 14, 2013 at 17:31 UTC||Need Help??|
I happen to prefer to do things this way, vs. mod_perl, because it keeps the Apache request-handlers small and also because it lets me deploy the FastCGI servers behind an internal firewall, where they are being fed by Apache/nginix servers that themselves donít have access to anything.
Even in a less sophisticated setup, FastCGI still allows to use different users for the webserver and the FastCGI process. So an administrator can grant only minimal privileges to both processes, whereas for mod_perl, the Apache process must have the sum of all privileges required by all mod_perl applications.
Another nice feature is that a crashing FastCGI application does not kill the web server, unlike a mod_perl application.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)