This is incorrect for Apache 2.4: In 2.4 there is async write completion.
SSL behavior is still like the worker MPM, due to design issues in mod_ssl and filter stack. This is unlikely to change until 3.0.
SSL behavior is still like the worker MPM, due to design issues in mod_ssl and filter stack. This is unlikely to change until 3.0.
server-info selections
MPM Name: event
MPM Information: Max Daemons: 1 Threaded: yes Forked: yes
server-status selections
1550 requests/sec - 1.6 GB/second - 1.1 MB/request
9 requests currently being processed, 41 idle workers
W__W_____W_W_______R______W______W_______W__W_____..............
................................................................
......................
If those are asynchronous response writing handlers in the sense that they could be handled by an event loop, why do they have their own threads?