Yes, I also saw in docs, FCGI needs a while loop around your code.
It could be possible to wrap codes in cgi files, like page.cgi. That should work, shouldn't?
The question is mainly not if is it possible or not (should be possible anyway), but if you want to add support for FastCGI or not, in a later LSQL release.
Speedy. Yes, in case of LSQL, using Speedy is much easier, since LSQL takes care about changing the shebang line in all cgi-s. But I have doubt, that this will be crossOS solution. Likely it will not work on Windows without further tricks (like creating /usr/bin/ dir & copy speedy to there). On Windows, Apache by default does not use the shebang line, but use registry to start Perl. As I know, registry feature can be turned off, but I never tried, yet.
About mod_perl. On channel #perl on ircnet, perl experts wrote:
- "running perldemons in the same address space as the webserver is borken",
- "everything that doesn't run in the same process space as the webserver is better than mod_perl",
- "with a fastcgi-like system you gain the speed of mod_perl _and_ a lot of extra security and functionality"
Q: "
What is the disadvantage of running scripts in the same process space as the webserver?"
A: "
1) security: if your CGI is borken, your server is toast
2) authentication: you MUST use as the apache user instead of the user you are
3) dispatching: you will run as many demons as there are apache processes, but there is no reason to think that the popularity of your script = popularity of your server
4) dependability: if my apache or perl coredumps, I don't want the other to die too"
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...