|
FastCGI is a protocol for integrating interactive programs into a web server. FastCGI is a variation on the earlier Common Gateway Interface (CGI); FastCGI's main aim is to lessen the burden on the web server imposed by each individual CGI program, allowing the server to scale up to handle many more concurrent requests.
History When handling each request to a CGI program, a traditional webserver will create a new process to handle the request. The CGI program is run in that process, the result sent, and then the process is discarded. Creating processes is a resource-expensive task, and each concurrent process imposes a nontrivial burden on the server. For this reason CGI based webservers under heavy load often experience significant slowdowns, or become mostly unresponsive. To address the scalability shortcomings of CGI, Open Market developed FastCGI and first introduced it their webserver product in the mid-1990s. Open Market originally developed FastCGI in part as a competitive response to Netscape's proprietary, in-process API (NSAPI) for developing Web applications. Implementation details Instead of creating a new process for every request, FastCGI uses a single persistent process which handles many requests over its lifetime. Processing of multiple requests simultaneously is achieved either by using a multi-threaded responder process, or with non-blocking I/O and an event loop. FastCGI also allows programs to get the web server to do certain simple operations, like reading in a file, before the request is handed over. Environment information and page requests are sent from the web server to the process over a TCP connection (for remote processes) or Unix domain sockets (for local processes). Responses are returned from the process to the web server over the same connection. The connection may be closed at the end of a response, but the web server and the process are left standing. Although initially developed by Open Market, FastCGI was implemented by a number of other webserver makers. The FastCGI approach, however, competed against other techniques which also aimed to speed and simplify server-subprogram communications, but which didn't follow the CGI paradigm. Apache modules such as mod_perl and mod_php appeared around the same time and seemed to be even better replacements for CGI, allowing closer integration with the core webserver. FastCGI languished for many years; however, later years have seen a resurgence in interest in FastCGI . Many web site administrators and programmers are finding that the separation of web applications from the web server in FastCGI (and the simpler SCGI) has many desirable advantages over embedded interpreters (mod_perl, mod_php, etc.). This separation allows server and application processes to be restarted independently — an important consideration for busy web sites. It also facilitates per-application security policies — important for ISPs and web hosting companies. It is possible to run a separate application process for each user; running with the user's assigned privileges, it can't affect the applications and data of other users. Web Servers Backend server FastCGI can be implemented in any language that supports sockets. API's exist for: FastCGI has enabled web application portability; in contrast, applications developed for embedded interpreters (such as mod_python) are often tightly bound to the Apache API. Recent frameworks such as Ruby on Rails, Catalyst, and Django allow use with either the embedded interpreters (mod_ruby, mod_perl, or mod_python respectively) or with FastCGI. | ||||||||
|
| |||||||||
 |
|
| |