httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Rooney" <roo...@electricjellyfish.net>
Subject Re: Should fastcgi be a proxy backend?
Date Mon, 06 Mar 2006 16:19:52 GMT
On 3/6/06, Plüm, Rüdiger, VIS <ruediger.pluem@vodafone.com> wrote:
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: rooneg@gmail.com
> >
> > We actually have a way to do that, it's the close_on_recycle flag, and
> > I had to turn it on in order to get anything approaching reliability
> > for fastcgi.  The problem with just using that is that without some
> > coordination between worker processes you're still going to end up
> > with collisions where more than one connection is made to a given
> > fastcgi process, and the majority of those don't know how to handle
>
> I think the problem is that we only manage connection pools that are local
> to the httpd processes.

Exactly, the pool of available backends needs to be managed globally,
which we don't currently have and it's not clear if that ability would
be useful outside of fastcgi.

-garrett

Mime
View raw message