There was a recent article in WebTechniques comparing the two
http://www.webtechniques.com/archives/2000/05/infrrevu/
-----Original Message-----
From: Scott Thomason [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 21, 2000 4:56 PM
To: [EMAIL PROTECTED]
Subject: re: mod_perl vs. FastCGI
You said:
> Most people on this list probably have already determined that
> mod_perl is better for their own needs. That`s why I`m here, at
> least.
>
> But "better" is a very subjective term, and you need to define your
> parameters. What are your goals, what are your constraints, what is
> your experience, etc., are all questions you need to answer before you
> can decide whether one technology is more suitable for you to use on a
> given project than any other technology.
OK, my goal is simple: I want my Perl scripts to run lightening fast,
ideally without bloating the memory requirements of my webserver. I'm a good
Perl developer. I've used mod_perl a little in the past, and spent many
agonizing hours cleaning up one-shot CGI scripts so they would work (and on
some, I just plain gave up and let them run slow). Last project, I gave
FastCGI a whirl (via mod_fastcgi and CGI::Fast) and was delightfully
surprised to find there was no headache involved, only benefit. Which got me
to wondering, why all the buzz over Apache::Registry if FastCGI offers the
same speed without the server bloat or coding restrictions?
So, given that, here's the question again: why would you choose
Apache::Registry over FastCGI? I want to be a believer...
---scott
