浏览 4659 次
锁定老帖子 主题:追溯fastcgi之历史
该帖已经被评为新手帖
|
|
---|---|
作者 | 正文 |
发表时间:2008-07-26
希望跟人探讨,对于这个的理解,能够让我明白fastcgi是如何一步一步开发并进入实用的,进而对fastcgi的基本原理有个全局的把握。 声明:ITeye文章版权属于作者,受法律保护。没有作者书面许可不得转载。
推荐链接
|
|
返回顶楼 | |
发表时间:2008-07-26
这些问题都可以通过google解决。
|
|
返回顶楼 | |
发表时间:2008-07-27
from wiki:
引用 CGI is a protocol for interfacing external applications to web servers. CGI applications run in a separate process, which is created at the start of each request and torn down at the end. This "one process per request" model makes CGI programs very simple to implement, but limits efficiency and scalability. At high loads, the operating system process creation and destruction overhead becomes significant and limits scalability. In addition, the CGI process model limits resource reuse techniques (such as reusing database connections, in-memory caching, etc.).
To address the scalability shortcomings of CGI, Open Market developed FastCGI and first introduced it in 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. 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. |
|
返回顶楼 | |