Add intra-process communication channel #276
Open
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
jrebelo
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.
This changes add an intra-process communication channel which allows all the participants created by the same Domain Participant Factory to communicate with each other without using the UDP communication channel. There is a channel per domain id to guarantee that participants in different domains remain in separate communication planes.
To enable the communication, the RtpsMessageRead and RtpsMessageWrite structs have been uniformized into one since they share the same representation.
To be able to make full use of this functionality there is also a new flag in the configuration that allows fully disabling the UDP, to prevent the sockets from being created and modifies the locator lists accordingly. UDP is now disabled for all the integration tests and benchmarks. Examples, interoperability tests and multi-machine tests remain with the default UDP enabled configuration.