so the single threaded select() loop, the java NIO...

# coroutines

[jimn]

so the single threaded select() loop, the java NIO dispatcher to onRead etc.. goes in launch(CommonPool) instead of CachedThreadPool.run(). in the past, On{Accept/Read/Write} handlers are do the IO in the single thread, but in kotlin can they be asyncronous coroutines running out of order ? i keep the IO in the single thread to reduce context overhead, but coroutines could seemingly queue up multiple io operations and clear the selector for more fetches without incurring a context switch