The other problem is that with NIO AsyncChannel yo...
# coroutines
e
The other problem is that with NIO AsyncChannel you don't have control on what thread pool it uses to invoke your callback (that is resume your coroutines). No control on sizing policies, anything. In a real high-load app you want to control all of that yourself.