Actually, I recently finished a FastCGI authenticator. The mod_fastcgi module provides
the equivalent hooks into the Apache authentication mechanism. It allows you to
configure httpd.conf in a manner nearly identical to normal basic authentication. But
the question remains: for speed, why Apache::Registry over FastCGI?
It wasn't memory leaks that gave me headaches with mod_perl...I couldn't get the
scripts to work correctly at all. I strongly suspect some obtuse use of globals was
screwing me up and causing the scripts to malfunction, but the script was to big,
elaborate, and messy for me to find it and I had to move on without the benefit of
mod_perl.
---scott
>>> Vivek Khera <[EMAIL PROTECTED]> 06/21/00 04:08PM >>>
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.
