atom feed39 messages in ru.sysoev.nginxRe: FCGI.pm ?
FromSent OnAttachments
Chris CorteseFeb 26, 2009 12:40 am 
mikeFeb 26, 2009 1:07 am 
Chris CorteseFeb 26, 2009 1:35 am 
Anoop AliasFeb 26, 2009 1:43 am 
Chris CorteseFeb 26, 2009 2:08 am 
Grzegorz NosekFeb 26, 2009 2:26 am 
Chris CorteseFeb 26, 2009 3:11 am 
Jim OhlsteinFeb 26, 2009 3:35 am 
Grzegorz NosekFeb 26, 2009 4:03 am 
mikeFeb 26, 2009 9:47 am 
Jim OhlsteinFeb 26, 2009 11:53 am 
Cliff WellsFeb 26, 2009 1:02 pm 
mikeFeb 26, 2009 2:19 pm 
Jim OhlsteinFeb 26, 2009 3:10 pm 
Chris CorteseFeb 27, 2009 2:31 am 
lubenFeb 27, 2009 6:11 am 
lubenFeb 27, 2009 6:40 am 
Grzegorz NosekFeb 28, 2009 4:17 am 
mikeFeb 28, 2009 2:03 pm 
Roger HooverMar 3, 2009 1:45 pm 
mikeMar 3, 2009 6:10 pm 
Roger HooverMar 3, 2009 8:08 pm 
Grzegorz NosekMar 4, 2009 12:40 am 
mikeMar 4, 2009 12:54 am 
Grzegorz NosekMar 4, 2009 1:42 am 
Jean-Philippe MoalMar 4, 2009 1:50 am 
mikeMar 4, 2009 2:14 am 
Roger HooverMar 4, 2009 9:03 am 
Roger HooverMar 4, 2009 9:23 am 
mikeMar 4, 2009 11:51 am 
Roger HooverMar 4, 2009 12:34 pm 
mikeMar 4, 2009 8:53 pm 
mikeMar 4, 2009 9:05 pm 
Roger HooverMar 5, 2009 9:22 am 
mikeMar 5, 2009 9:55 am 
Roger HooverMar 5, 2009 12:25 pm 
mikeMar 5, 2009 4:15 pm 
Roger HooverMar 6, 2009 5:21 pm 
mikeMar 6, 2009 6:16 pm 
Subject:Re: FCGI.pm ?
From:mike (mike@gmail.com)
Date:Mar 4, 2009 2:14:30 am
List:ru.sysoev.nginx

i am all for someone taking Grzegorz's work, and instead using the perl launcher or spawn-fcgi, maybe add a bit more intelligence behind it and make it simple for launching pools under different uid/gid with different child counts, etc.

On Wed, Mar 4, 2009 at 1:50 AM, Jean-Philippe Moal <skat@skateinmars.net> wrote:

Grzegorz Nosek a écrit :

On wto, mar 03, 2009 at 08:09:12 -0800, Roger Hoover wrote:

For dynamically spawned processes, if someone were willing to write an nginx module to call supervisord's XML-RPC api, we'd have a complete, language-agnostic replacement solution for mod_fastcgi.

XMLRPC sounds evil ;) My checklist for required features looks like below, how far is supervisord from meeting that?  - killing idle processes after some timeout (with a configurable    signal, preferably)  - static pool size management (keep 5 of those running at all times)  - dynamic pool size management (keep 1-5 running depending on load;    this will require congestion notifications from the web server, like    you said)  - process status notifications ("foo failed to run, what now?", with    some mildly intelligent retry logic) -- I need to alert an external    entity somehow.  - easily generated configuration file

I don't use it but God (http://god.rubyforge.org/) seems to respond to your
needs.

If supervisord can do that, I'd be willing to write an Nginx module to interface with that, sometime in this millenium.

Best regards,  Grzegorz Nosek