Re: pending connections

Andrej,

If you have only one fast-cgi instance, and send 100 requests, the other 99 will 
block in httpd waiting for the accept() to the FastCGI socket to succeed. 
Whether or not they timeout is a function of the client browser, your 
httpd/fastcgi settings, etc.  The number of requests that can wait before 
getting connection refused is defined by the request queue (defaults to your TCP 
wait queue, I think, but changable with a FastCGI parameter).

However, keep in mind that the keepalive to the client is usually handled by the 
httpd process, not by the FastCGI process.  In an ideal world, the httpd handles 
the response to the request, and the FastCGI process is then free to process the 
next response.

The application you describe would not be a good match for FastCGI.

David.

-----

On Tue, 29 Nov 2005, Andrej van der Zee wrote:

> Hi,
>
> I have a question about pending connections. Suppose I have only one fast-cgi 
> instance running and I send simultaneously 100 requests. Now the first 
> request that is accepted takes 20 minutes. We will do some tricks to keep the 
> connection to the client alive. What happens to the pending 99 requests? Are 
> they being timeout by the kernel before they will be accepted by fast-cgi? 
> Does anybody has experience with this? I am working on a 2.6.12+ kernels.
>
> Greets,
>
> Andrej
>
>
> ___________________________________
> fastcgi-developers mailing list
> http://fastcgi.com/fastcgi-developers/
>

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/