I'm new to supervisor and would like a capability that takes the fcgi-program feature one more step.
What I want is for supervisord to create a socket (like it does for fcgi-program), but then also do the accept on it. Each time a connection comes in, spawn the child process and hand-off the connection to the new child. From that point forward, supervisord is not involved in the communication between the connecting client and the spawned server. The reason I want this is to give the client control over how many server processes are spawned. Supervisord would create the socket when it starts, but not spawn any of these type of processes until connections come in. This is a case where I am writing both the client and server, and the server is only visible on the internal network. A. Does anybody know if something like this already exists? B. For those "in the know" on the internal architecture of supervisor, what pointers do you have on how to implement this? C. Is anybody else interested in something like this, and if so, what would you like to see in it (no promises though). Thanks! -Bruce
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
