AW: Dynamic but persistent fastCGI process?

Hello Brian,

Have you tried:

FastCgiConfig -maxClassProcesses 1

Erich Prchal
Siemens Austria PSE


-----Ursprungliche Nachricht-----
Von:
fastcgi-developers-bounces+erich.prchal=siemens.at-xGejAJT2w6yOE5Ap4OspEtHuzzzSOjJt@public.gmane.org
[mailto:fastcgi-developers-bounces+erich.prchal=siemens.at-xGejAJT2w6z22ue2IjjDuw@public.gmane.org
ea.net]Im Auftrag von Brian K Justice
Gesendet: Freitag, 05. November 2004 04:56
An: [email protected]
Betreff: [FASTCGI] Dynamic but persistent fastCGI process?


Hello --

I am using FastCGI for several static processes started per my Apache
httpd.conf file (under Linux), and this works great. What I am also hoping
to do is to have a dynamic process which is not automatically started, but
that will continue to live once started. What I am seeing is a request for
my FastCGI app (say http://brian/fcgi/dynamic/doit) starts the doit process.
Then if I make another request (POST) for the same thing, I get a *new*
process, but I want to access the one just started prior to that.

In my httpd.conf I have:

<Directory /usr2/httpd/fcgi-bin/dynamic/>
	SetHandler fastcgi-script
	Options +ExecCGI
</Directory>

Is there a way to specify that once something starts from that dynamic
directory that any new requests for it are handled by it instead of having a
second process start -- or am I missing some obvious thing here?

Hope this made sense.

Thanks.

Brian

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