Option communication config #241
Merged
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
As we are not currently using zenoh communication, it would be preferable to not mention it in the datalflow graph as some people might: - A. confuse it with our shared memory. - B. Question why it is there. - C. Question what is zenoh. I think that we can support dora-rs without external communication config, as I can see many use-case in simulation.
haixuanTao
force-pushed
the
optionable-communication-config
branch
from
67368e4 to
6ad1cab
Compare
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.
As we are not currently using zenoh communication, it would be preferable to not mention it in the datalflow graph as some people might:
I think that we can support dora-rs without external communication config, as I can see many use-case in simulation.