What is the fastcgi?

FastCgi is an extension of the Common Gateway Interface (CGI) interface (CGI), which has been developed by an extinct company called Open Market. Fastcgi is freely available as an open standard. It solves certain shortcomings in CGI that reduce performance.

Unlike CGI, Fastcgi does not create a new process for each requirement, minimizing the direction of creating and destroying the process every time the request is accepted. This direction can be bypassed using the application programs (API) interfaces, such as Netscape Server Programming Interfaces (NSAPI) or Internet Application Programming (ISAPI), but because it is proprietary, there is another learning curve and limitation in supported languages ​​to be considered. Another lack of CGI is that certain cases cannot be obtained for reuse, such as databases or techniques of storage. Manipulation with requirements can be up to 30 times faster using fastcgi compared to conventional CGI.

with RychmCgi, multiple requirements can be processed into one connection known as multiplexing. Alternatively, more connections can be used. Requirements are transmitted by means of a file transfer (FTP) or sockets. The same connection is then used to return the answer.

Although the connection can be closed at this point, the web server and the process still persist. This offers many advantages. For example, this means that the server process and applying the application can be turned off or restart separately.

FastCgi was originally developed on Open Market and implemented in its web server menu. However, the interface can be implemented on any server and has soon been introduced on a number of other industrial web servers. Fastcgi is highly compatible with the distributed calculation, so FastCGI can be launched on a separate server on the web. It offers all the advantage of the availability of systems, improvement of scalablesTheness and increasing system security because the components are isolated. The use of remote fastcgi is less management, as the internal network can handle applications.

Like CGI, CGI can generate the answer from the hyperl transmission protocol (HTTP) request, so it can also fastcgi. It also processes tasks such as verification and data conversion. These tasks are processed using roles that can be added and extended freely.

FastCgi is easy to understand and will run with almost any programming language. Processes are isolated so servers cannot be infected with application specific problems. Any application created with FastCgi is backward and old servers are running CGI. In addition, the library of applications is designed to make it easier to migrate CGI applications.