[FASTCGI] FastCGI, Comet and Client Link failure
Howard.May at dialogic.com
Thu Jan 14 10:37:49 EST 2010
I start a new comet connection after I accept a FCGX_Accept_r returns a FCGX_Request with a URL of "http://<my server>/new_comet_connection_please". I can then send chunks down this connection using FCGX_FPrintF. I do not call FCGX_Finish_r for this request because I want to leave the HTTP transaction open for further data.
So fastCGI is giving me access to a new HTTP transaction and the FCGXFPrintF function allows my fastcgi application to send chunks to the web server (Abyss at present) to pass to the remote Client. So far so good. My problem is that at some point the TCP connection to the Client may die and I don't at present have any way of detecting this.
From: Jay Sprenkle [mailto:jsprenkle at gmail.com]
Sent: 14 January 2010 15:24
To: Howard May
Cc: fastcgi-developers at mailman.fastcgi.com
Subject: Re: [FASTCGI] FastCGI, Comet and Client Link failure
fastcgi is a transactional style application. If you want to run a persistent program you probably want the fastcgi application to communicate requests to, and retrieve status from, the daemon/service that implements your comet connection.
On Thu, Jan 14, 2010 at 6:23 AM, Howard May <Howard.May at dialogic.com<mailto:Howard.May at dialogic.com>> wrote:
Consider a simple fastCGI application with a comet connection to a remote Client. The application is periodically sending chunks to the Client but at some point the Client connection fails. How and when does the fastCGI application learn about this?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FastCGI-developers