http://www.perlmonks.org?node_id=985806


in reply to Re^2: Misery: trying to get mod_perl working on Windows 2008
in thread Misery: trying to get mod_perl working on Windows 2008

Why are you recommending NOT to run mod_perl?

Well, there are some reasons not to use mod_perl. The main reason is that there is only one Perl interpreter instance (actually, there is one per worker process, cloned around forking the worker process). It runs inside the Apache process. Forking and cloning may cause some minor trouble, but that's rarely a problem. Mostly, this affects DBI, and Apache::DBI knows enough of DBIs internals to handle most of the problem. On Windows, Apache does not fork (as far as I know), but creates threads instead. So, everything runs in a single process.

The real problems are:

So, applications are de facto not isolated from each another, and you can not use operating system permissions to limit access to only one application or to the web server.

Compare with FastCGI:

Of course, because FastCGI runs outside the Apache server, you have some communication overhead. And you can't use all of the Apache internals that mod_perl offers but rarely anyone uses.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
  • Comment on Re^3: Misery: trying to get mod_perl working on Windows 2008

Replies are listed 'Best First'.
Re^4: Misery: trying to get mod_perl working on Windows 2008
by rpnoble419 (Pilgrim) on Aug 06, 2012 at 21:27 UTC
    Thank you for your thoughts on this. I had a discussion with a friend of mine and I had the same issues you just brought up about the Perl interpreter instance. I did not know about the other issues, so again thank you for enlightening me...