Currently, we always launch our TX and RX threads, which sit in blocking I/O. Some users might prefer to explicitly manage the I/O in the context of a non-blocking event system (e.g. epoll() or kqueue()). We ought add an option to the options struct allowing this mode to be requested, and add the necessary API.
Currently, we always launch our TX and RX threads, which sit in blocking I/O. Some users might prefer to explicitly manage the I/O in the context of a non-blocking event system (e.g.
epoll()orkqueue()). We ought add an option to the options struct allowing this mode to be requested, and add the necessary API.