I am going to start a cgi-fpm project. The goals will be aligned like php-fpm except slightly modified for the differences with cgi and fastcgi. It might not be able to support adaptive spawning without some sort of api or tools but at least will make management easier and not require third party tools. It will basically enhance fcgiwrap with php-fpm style configuration and hooks for external control for things like an nginx module.

The annoyances with cgi and fastcgi can be discussed and hopefully addressed.

Thoughts?

Also this could just be an nginx module too. But it would add some weight and require suexec type stuff. So probably not a good idea.

Let me throw together a quick list of ideas.

On Mar 4, 2009, at 12:34 PM, Roger Hoover <roge...@gmail.com> wrote:

On Wed, Mar 4, 2009 at 11:51 AM, mike < <mike...@gmail.com> mike...@gmail.com> wrote:

The approach you describe assumes that the parent process can intercept socket connections as they come in. I don't think this is possible within the constraints of the FastCGI spec. Each FastCGI process is forked with file descriptor 0 pointing to a shared FastCGI socket and each child process just calls accept() on that socket. The OS is responsible to determining which process in the pool accepts each request so there's no way for the parent process to keep track of which child is taking which request. Unless that information can be retrieved from the kernel, I think the only place that load logic can be implemented is in an nginx module.