Right now the on-read callback for a zmq-socket drains the 0MQ socket in a blocking function in the I/O callback until the read would block before returning from the callback.
Instead, the on-read callback should start a high-priority idle watcher (Higher than the delivery watcher, and if this approach is taken the priority values should be externalized to something resembling constants) which will then drain the socket until it would block, before resuming the IO callback.
Right now the
on-readcallback for azmq-socketdrains the 0MQ socket in a blocking function in the I/O callback until the read would block before returning from the callback.Instead, the
on-readcallback should start a high-priority idle watcher (Higher than the delivery watcher, and if this approach is taken the priority values should be externalized to something resembling constants) which will then drain the socket until it would block, before resuming the IO callback.