rest/cgi: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
Line 1: Line 1:
Obsoleted by [http://rubyforge.org/projects/mongrel/ Mongrel]
Obsoleted by [http://rubyforge.org/projects/mongrel/ Mongrel]


= SFCGI: Beyond FastCGI? =
8CEhSA  <a href="http://kilbehjwcohd.com/">kilbehjwcohd</a>, [url=http://omffynyntfcr.com/]omffynyntfcr[/url], [link=http://occvjkboppqu.com/]occvjkboppqu[/link], http://cmjxzxbgjwse.com/
 
Currently the optimal way for a web server to invoke a web application is [http://www.fastcgi.com/ FastCGI].  This provides huge performance [http://www.fastcgi.com/devkit/doc/fastcgi-whitepaper/fastcgi.htm wins over regular CGI], and has succeeded in eliminating the need for proprietary, language-based web server APIs. FastCGI supported by pretty much every modern webserver, and is recommend by most web development platforms (PHP, Rails, TurboGears, etc.).
 
== The Problem ==
 
What's not to love?  Well, the one disadvantage FastCGI has relative to CGI is the ability to trivially support scripts.  Under CGI, a script could just get the parameters from envars, and read stdin and write stdout.  What could be simpler?  Now, scripts need to link into a (reasonably complex) library that speaks the FastCGI protocol in order to do anything, which also means they can't be tested from the command-line.
 
Is there a way to do CGI that is comparable in efficiency to FastCGI, but more script-friendly? A Script-friendly CGI, or Scriptable Fast CGI (SFCGI), if you will?
 
Is such a thing possible?
 
Would anyone care even if it were, since FastCGI libraries are readily available?
 
== Alternatives ==
 
; [http://www.python.org/peps/pep-0333.html WSGI]:Web Services Gateway Interface
; [http://python.ca/nas/scgi/protocol.txt SCGI]:A Simple Common Gateway Interface alternative

Revision as of 18:05, 17 November 2008

Obsoleted by Mongrel

8CEhSA <a href="http://kilbehjwcohd.com/">kilbehjwcohd</a>, [url=http://omffynyntfcr.com/]omffynyntfcr[/url], [link=http://occvjkboppqu.com/]occvjkboppqu[/link], http://cmjxzxbgjwse.com/