Because mod_perl is soo much cooler!
(... ducking ...)
Seriously, I bet there's a lot more demand for competent mod_perl
hackers out there. The mailing list is always screaming "we can't find
enough people to do this XYZ-startup.com project". FastCGI is just a cool
way of not firing off processes on each CGI hit, but mod_perl permits
full access back to the Apache API to some some wild and wacky stuff.
-- Randal L. Schwartz, Perl hacker | [reply] |
You don't have to duck you, mod_perl is really a lot cooler
(and more powerful anyway), but also more complicated and
has more dependencies. For my current projects, i also use
mod_perl.
For kael: FastCGI
starts you CGI (not only perl, but who needs something else)
as a seperate process. Apache with the FastCGI module than
communicates trough a socket (or even IP) with this CGI process.
The benefit is, as Randal said, that the Webserver doesn't
have to spawn a new process for every request.
FastCGI is a good way, if you just want you CGIs to be faster
(referring to the startup time) and don't like to "bother"
with mod_perl. For everything else, mod_perl is the way to go.
Roli
| [reply] |
