Re^6: Perl is dying

You should use a reverse proxy setup or similar for that, as described in the mod_perl docs, or use FastCGI.

Or both. There's a new kid on the web servers block, putting pressure onto Apache: Lighttpd AKA "Lighty". It doesn't have mod_perl, obviously (as mod_perl is Apache technology), but instead, it puts a heavy focus onto FastCGI and proxying.

Comment on Re^6: Perl is dying

Replies are listed 'Best First'.
Re^7: Perl is dying by perrin (Chancellor) on Jul 15, 2006 at 02:58 UTC
How is that "both"? It runs FastCGI in essentially the same way as Apache, doesn't it?	[reply]
Re^8: Perl is dying by bart (Canon) on Jul 15, 2006 at 21:23 UTC
You could say that, yes, except that until recently, Apache's support for FastCGI was crap. The technology was essentially abandoned for 5 years, until they picked it up again a few months ago. Why? Because they can feel the pressure, from Lighttpd, for one. Other platforms, like Zope, Ruby On Rails, and even PHP, apparently prefer to use FastCGI or similar technologies to an embedded interpreter. I think it would be a better alternative to mod_perl, too, because, well, if each website has its own persistent Perl environment (which I can envision to actually be much like mod_perl), they can't crash each other. The scripts interpeter would be running independently of the webserver, so it can't touch the internals of the webserver either. As a whole, this looks to me like it would be a lot like the "mod_perl light" the OP was dreaming out loud about.	[reply]