Does a single thread per channel model with Netty OIO mean that either write or read operation can be executed on a single channel at a time? I am writing distributed applications with a small number of connections (~20) and I was thinking of using Netty OIO. However, it is very important for me not to be blocked on receiving messages on some channel while corresponding worker thread is blocked with writing? Is there a way to achieve this with Netty OIO, i.e., can I have one thread for writing on a channel and one thread for reading on the same channel?