Re: Directives in Apache

FactCgiConfig is used to set the default parameters, such as connection and 
idle timeout. Whatever is specified using this directive applies to all fast 
cgi instances. It's not required but can come in handy if the same directive 
is to be applied to more than one instance.

FastCgiConfig defines a dynamically handled fastcgi instance, that is the 
application will be started and handled by the web server (actually by the 
fastcgi module's process manager), if it goes down a new instance will be 
started.

The following will define /var/web/fcgiappname as a fastcgi instance, it 
will be started with the environment variable NAME set to value and be 
exposed as /app.

FastCgiServer /var/web/fcgiappname -initial-env NAME=value
ScriptAlias /app /var/web/fcgiappname

FastCgiExternalServer on the other hand defines an external fastcgi 
instance,the application will not be either started or handled 
automatically, that's up to the user, hence the name external.In this case 
the web server/fastcgi module will act like a proxy and forward all suitable 
requests to the server.

FastCgiExternalServer /app -host localhost:4080 -initial-env NAME=value
ScriptAlias /app /app

--
Emil A Eklund
([email protected])

----- Original Message ----- 
From: "Tom Allison" <[email protected]>
To: <fastcgi-developers-xGejAJT2w6yOE5Ap4OspEtHuzzzSOjJt@public.gmane.org>
Sent: Monday, June 05, 2006 03:32
Subject: [FASTCGI] Directives in Apache


Can someone explain the differences between:
FastCgiServer
FastCgiConfig
FastCgiExternalServer

and maybe how to use them, or just point me to a location that explains the
differences.

I've been here:

        http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html

without much luck
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/ 

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