Re: FastCgiExternalServer vs FastCgiServer for runing php-fastcgi

There is no downside I know of. The communication is done over unix socket in
both cases, you just share the same pool of FastCGI PHP processes. For example,
if you have more than one vhost under the same UID, you would use this to share
the same FPHP pool instead of having a separate one for each vhost, thus using
less server resources. There is rarely a case where you would want to have 2 or
more separate FPHP pools for the same UID spread among different vhosts. Read
up on FastCgiExternalServer w/ unix sockets and you will understand how to do this.

-Simon

On Mon, 18 Oct 2004 13:30:37 -0600, Ken Gunderson wrote:

>On Monday 18 October 2004 11:48 am, Simon wrote:
>> Using FastCgiExternalServer you can share the same FPHP pool among
>> different vhosts with FPHP pool running on the same machine.
>
>[snip]
>
>And the downside of doing this would be?  I figure there must be one, 
>else the FAQ would provide an external example instead??  Also, would 
>you mind elaborating a bit?  
>
>Thanks for your insights.
>
>-- 
>Best regards,
>
>Ken Gunderson
>GPG Key-- 9F5179FD
>
>"Freedom begins between the ears."      -- Edward Abbey
>



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