Talk:FastCGI
From Wikipedia, the free encyclopedia
"FastCGI' is a rethinking of CGI providing better scalability."
I agree the original wording was misleading, but the word "rethinking" does really sit well when refering to a standardised protocol. I like the way it is described on cryp.to: "FastCGI is a variation of the CGI interface". Let me know if you have a problem with that or can conjure a better phrase. Jayvdb 09:17, 20 March 2006 (UTC)
[edit] FastCGI's resurgence
We need to provide some concrete evidence to support our assertion that FastCGI has enjoyed something of a resurgence (indeed we really should provide a reference that supports our "FastCGI: the wilderness years" assertion too). -- Finlay McWalter | Talk 00:01, 15 July 2006 (UTC)
- I know we really need a source. I wrote that based on my own observations, like a few blogs (example). The only numbers I can find is in Security Space's web server survey, but doesn't appear to show any sudden surge. Numbers for FastCGI will probably be hard to find. That survey only lists Apache modules, and the page is only for 'mod_fastcgi' (only Apache 1?). On my Apache 2 server here, mod_fcgid doesn't add a signature to the 'Server:' line. There are also other web servers using FastCGI, like LigHTTPD and Zeus, and I don't know if there's a good way of figuring out if they're using FastCGI either.
- Probably the only reliable thing to go on is the appearance of frameworks using/allowing FastCGI, e.g the ones mentioned in the article - Catalyst, RoR, and Django. --Imroy 02:18, 15 July 2006 (UTC)
[edit] Connection handling
I removed all references to one connection per request since that's not always the case. Would mentioning that the protocol allows multiplexing multiple simultaneous requests over one connection be too much detail? Bo Lindbergh 14:28, 22 July 2006 (UTC)
- Sure, that sounds worthwhile. -- Finlay McWalter | Talk 16:50, 22 July 2006 (UTC)
