On Fri, May 13, 2016 at 7:02 AM, Stefan Eissing <stefan.eiss...@greenbytes.de> wrote: > That would allow HTTP/2 processing to become fully async and it would no > longer need its own worker thread pool, at least with mpm_event. > > Thoughts?
One bit I am still ignorant of is all of the beam-ish stuff (the problem and the solution) and how moving the main connection from thread-to-thread might impact that. Maybe you could have a pipe() with a writing end in each slave, and read by the master, that the event loop watches to re-schedule the master? -- Eric Covener cove...@gmail.com
