|
in reply to Re^3: Perl is dying
in thread Perl is dying
Which is, ironically, why I use FastCGI. mod_perl is too heavy for my needs (80% of my web requests don't require Perl in every HTTP process). I tried PersistentPerl/SpeedyCGI, liked it, but found a couple of bugs and the maintainer seems to have disappeared. I thought FastCGI was pretty much dead, then discovered that it's what Rails uses. Since it seems to be getting a new audience, I figured that I wouldn't be left in the lurch like I was with PersistentPerl. |
Re^5: Perl is dying
by perrin (Chancellor) on Jul 14, 2006 at 20:21 UTC
|
Yeah, I don't recommend using mod_perl to serve static files on a site with much traffic. You should use a reverse proxy setup or similar for that, as described in the mod_perl docs, or use FastCGI. The nice thing about FastCGI's new popularity is it means ISPs are getting pressure to support it. | [reply] |
|
|
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.
| [reply] |
|
|
How is that "both"? It runs FastCGI in essentially the same way as Apache, doesn't it?
| [reply] |
|
|
|
