>>>>> "ST" == Scott Thomason <[EMAIL PROTECTED]> writes:
ST> in the past, and spent many agonizing hours cleaning up one-shot
ST> CGI scripts so they would work (and on some, I just plain gave up
ST> and let them run slow). Last project, I gave FastCGI a whirl (via
I wonder how these scripts on which you gave up would work with
FastCGI. I suspect they have memory leaks.
If you write your perl programs well, that is, with "use strict" and
warnings turned on, and you get a clean execution, then moving those
to mod_perl is pretty much trivial. You just need to be careful about
global variables.
Another reason to use mod_perl is that you're not just getting the
ability to write CGI programs. You get the ability to interact with
Apache at *any* phase of its API using perl. That is, if I want to
write my own authentication mechanism, I can do it in perl. I don't
think you can accomplish that in FastCGI, since this is not a CGI
operation, it is a web-server operation.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: [EMAIL PROTECTED] Rockville, MD +1-301-545-6996
GPG & MIME spoken here http://www.khera.org/~vivek/
