Re: Handling multiple simultaneous TCP connections

On Jun 15, 2006, at 12:57, Basile STARYNKEVITCH wrote:

> Le Wed, Jun 14, 2006 at 03:38:12PM +0400, Keith Martin écrivait/wrote:
>
>> Basically what I am trying to achieve is a fast-cgi handler that 
>> listens to
>> a given TCP/IP socket, and as soon as a connection is made if forks a 
>> child
>> to handle that connection (accepting and dealing with that fcgi 
>> request
>> etc), whilst the parent immediately goes back to waiting for a new
>> connection.
>
> In my humble opinion, this is the case where a simple ordinary CGI 
> approach
> (not a FastCGI one) works better. If for bizarre reasons you really 
> need
> a FastCGI server, use a fastcgi to CGI wrapper and then try to convince
> your management (or client) that a plain CGI is more suitable.

Well, that heavily depends on the amount of initialization your cgi 
have to do. Not to mention the overhead starting each time a new 
process. FastCGI also simplify some designs, like sharing data among 
threads, which cannot be easily stored inside files or db.
-- 
Thierry Pierron


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