Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZeroMQ sockets should not drain in a blocking manner on-read #5

Open
sshirokov opened this issue May 10, 2012 · 1 comment
Open

ZeroMQ sockets should not drain in a blocking manner on-read #5

sshirokov opened this issue May 10, 2012 · 1 comment

Comments

@sshirokov
Copy link
Owner

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.

@sshirokov
Copy link
Owner Author

Should wait on #8 and use the resulting API in a higher priority queue to drain the socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant