problem: pub/sub pattern in zeromq is complicated and not thread safe #1727
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c-rack
added a commit
that referenced
this pull request
Jan 27, 2016
problem: pub/sub pattern in zeromq is complicated and not thread safe
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
suggestion solution: making new pattern, radio-dish.
radio-dish pattern is thread safe, therefore is single frame protocol.
API is simplified as well, instead of zmq_setsockopt, you can call zmq_join and zmq_leave.
Radio-dish matching is exact matching (vs prefix of pubsub).
Groups are NULL terminated string. message must start with the group, NULL and than the message.