In what sense is Apache 2.4.2's event mpm event-based when this is the result of siege -c 1000 http://hostname:port/sample.txt http://hostname:port/sample.txt

In what sense is Apache 2.4.2's event mpm event-based when this is the result of siege -c 1000 http://hostname:port/sample.txt http://hostname:port/sample.txt 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?