Can&#x27;t completly understand the main message of what is proposed here.<p>Using multiple threads were one thread accepts connections and others process the connections is already quite standard (e.g. look on how Netty for Java works with a boss thread and worker threads).<p>However the pattern won&#x27;t work with blocking IO like it&#x27;s suggested in the referred page if your worker thread should handle multiple connections. Even if poll tells you the connection is readable there might not be enough data for a complete request - so you need a state machine for reading again. Or you block until you have read a complete request and thereby block other connections that should be served by the same thread(pool). And if you block on writing responses then one slow connection will block the processing of the others.<p>What also should be considered is that by far not all network protocols follow a pure request -&gt; response model. If the server may send responses asynchronously (out of order) or if there is multicast&#x2F;broadcast support in the protocol the requirements on software architecture look different.