Re: A junior question

 When you write a FastCGI app, you make a FastCGI server. The webserver
is your client.

Your FastCGI app listens for requests from clients (the webserver),
processes the request, and returns the result. That means you have a
server, ie a FastCGI server.

To my knowledge, FastCGI apps cannot function as a standalone webserver
unless there is a separate module written which can receive and process
HTTP requests from a web client (browser). There is no HTTP server
module included with the FastCGI libraries.

It is entirely possible to produce a FastCGI executable that can also
function as an HTTP server, but you have to write the HTTP server part
and design the app so that at some point, the application part of the
code can work whether the requests are coming from FastCGI clients or
HTTP clients.


On 08/31/2010 05:03 AM, Omar Li wrote:
>
> 	
>
> Hi , All ,
>
> I’m a junior for FastCGI and have a basic question.
>
> I look at some websites which say that FastCGI is not only a
> performance of fast CGI but also could perform as a web server.
>
> I don’t know it is a right argument ?
>
> thanks.
>
> Omar
>
>
> 	
>
>
>
> _______________________________________________
> FastCGI-developers mailing list
> [email protected]
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers

_______________________________________________
FastCGI-developers mailing list
[email protected]
http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers