Hi, I would like to know more about the process flow of the event MPM. The docs indicate it was largely about moving listening logic for keep-alives out of the worker threads and into the listener thread. The name implies to me that it might be more general than that (for example, supporting a more cooperative task management with the working threads).
My interest is that I would like to know if the event MPM is on the path to support content handlers that utilize Asynchrous/non-blocking I/O. So that the content handler could yield control back to worker thread so a new task could be scheduled to it while the previous task waits for the async I/O to wakeup. Make sense? Ludicrous? All feedback welcome. Please help point me in the right direction. For example, if the event MPM is the right place to start, or a whole new MPM would have to be written? Thanks for your advice. -Scott ([EMAIL PROTECTED])
