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
Move monitoring functionality out of socket_t and into monitor_t #22
Conversation
As already said in the other thread: In ØMQ 3.3 the notification messages consist of 2 parts. |
… guaranteed to get monitor events after this point. This is useful if you are spawning the monitor to a different thread and need to wait until monitor has started before opening the socket.
…ONITOR_STOPPED event.
Abort now implemented. |
Hello all Is there any reason why we couldn't merge this PR? Cheers |
Yes, that is correct. Just waiting for a maintainer to merge it, there doesn't seem to be a particularly active one for this project. |
Let's merge it then! |
Move monitoring functionality out of socket_t and into monitor_t
Thanks |
@ricnewton I've pushed you up to committer, take a look at http://rfc.zeromq.org/spec:22 which is our process. |
Some comments on these changes in pull request 21: #21