Re^7: mod_perl, and weird caching

If you have another option (fcgi, for example). make use of that on a shared host where those are your only two options. mod_perl on a shared apache instance where you don't have complete control over the apache instance is not (IIRC) a secure configuration.

--MidLifeXis

Comment on Re^7: mod_perl, and weird caching

Replies are listed 'Best First'.
Re^8: mod_perl, and weird caching by ultranerds (Hermit) on Feb 05, 2014 at 07:55 UTC
Hi, Would that work though, if we wanted caching on multiple sites? We currently have about 5 sites we'd love to get onto mod_perl (or some caching system) TIA Andy	[reply]
Re^9: mod_perl, and weird caching by afoken (Chancellor) on Feb 05, 2014 at 19:04 UTC
You should really consider using FastCGI. FastCGI keeps Perl and your program in memory, like mod_perl does. But FastCGI runs in a separate process, one per application. This keeps different configurations in different processes. You can even use different user accounts for different applications. A crashing application does not kill the webserver. FastCGI does not depend on one specific webserver, any FastCGI compatible webserver will do. Of course, FastCGI has the disadvantage of having several instances of Perl running instead of just one (so it may use more memory). And it has a little bit more overhead because it needs inter-process communication between webserver and perl, where mod_perl just calls functions. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]