Add support for true multipart in pub/sub messages #64
Conversation
This file contains 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
t-b
changed the title
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.
The PUB/SUB sockets always used multipart messages. One message for the filter the other one for the message. But now we want to pass more message parts.
The idea is that the 1D wave reference wave holds one wave for each message part. The wave contents are then used as message, text wave must be single point only. For receiving we will initially create unsigned 8bit integer waves for the contents (!?) or we could take a hint from the wave types of empty waves in the wave reference wave.
Use case: AllenInstitute/MIES#2230 (comment)