[Fwd: Re: apache 2.x and mod_fcgi-- revived?]

Hi All

Following up on adding to the issues list.

I have a PHP application suite which uses fastcgi to serve persistant 
connections to an application server for things such as database access 
and other services.

I had a requirement for each application that a user started to have a 
single dedicated server process per application. A user can start many 
applications in one session. I looked at the session affinity patches 
but concluded that they were not suitable.

My solution has been to use a fatscgi broker process to create unique 
symbolic links to the main application process in the fcgi-bin 
directory. PHP then opens a connection to that unique process as a 
dynamic fastcgi application. I have also made some small changes to 
fcgi_pm to catch a termination signal (99) from the process to stop 
respawning. However this is not perfect as it does not reuse or free the 
memory allocation. I was reluctant to make too many changes.

My request would be that there is a mechanism in mod_fastcgi that allows 
the startup of a unique dedicated fastcgi process with a means of 
telling it to shut down and not restart. Having looked back through the 
archives I see that this or similar requirements are quite common.

Shaun Coughlin
-- 

Shaun Coughlin
Managing Director

Tel: 01827 304100
Fax: 01827 310526

www.traderman.co.uk

Intelligent Software for Transport and Warehousing 



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