Hi Greg, This is nice stuff. Process management is one of the incomplete areas. If I was doing this in CZMQ, I'd have a class that managed child processes and sent events (DIED, ENDED) back to the parent over a pipe.
-Pieter On Wed, Dec 18, 2013 at 3:33 PM, Greg Ward <[email protected]> wrote: > On 27 November 2013, I said: >> I'm hacking on a task distribution system used internally here. It has >> N masters sending tasks (shell commands) out to M workers, and then >> doing stuff with the results. There's something that annoys me >> slightly about the implementation: the worker runs each task in a >> separate thread. >> >> IMHO it would be ever so much nicer to just spawn the child process >> that runs a task, and harvest the results when they are ready. IOW, I >> want to integrate wait() and zmq_poll() in a single event loop. > > Thanks again to Michael Haberle for the tips. Since this was > non-obvious to me, I assume it will be non-obvious to others in > future. So I made several working examples and wrote up a blog post: > > http://gerg.ca/blog/post/2013/zmq-child-process/ > > Comments/criticisms are welcome. > > Greg > -- > Greg Ward http://www.gerg.ca > <[email protected]> @gergdotca > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
