It's actually "cgi-fcgi" ... code/docs are here :What would be the cgi2fastcgi bridge - does it have any advantages over SpeedyCGI? I didn't find anything regarding this on google.
http://www.fastcgi.com/devkit/doc/overview.html
The primary advantage of FastCGI is something I don't think you care about: portability. You can run code in a high performance (persistent interps/db connections) way identically across many different web servers and operating systems. The protocol has some support for authentication and filtering stages (the kind of thing you get using a web server's native API), but it's pretty weak in practice.
Since it sounds like you're just looking to simplify your applications setup, I would go with Speedy because it's more actively developed than the cgi-fcgi bridge and probably simpler.
John http://www.jsequeira.com
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
