Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cross-Vendor communication is not guaranteed by design. #4736

Merged
merged 2 commits into from
Sep 23, 2024
Merged

Cross-Vendor communication is not guaranteed by design. #4736

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1cf0055
Cross-Vendor communication is not guaranteed by design.
fujitatomoya Sep 12, 2024
f2bfb2b
rewrite the description from review.
fujitatomoya Sep 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,3 +83,9 @@ For example, if both ``rmw_cyclonedds_cpp`` and ``rmw_connextdds`` ROS packages
If ``rmw_fastrtps_cpp`` is ever installed, it would be the default.

See the :doc:`guide <../../How-To-Guides/Working-with-multiple-RMW-implementations>` for how to specify which RMW implementation is to be used when running the ROS 2 examples.

Cross-Vendor Communication
--------------------------

While different RMW implementations may be compatible in limited circumstances, this is not guaranteed.
Thus it is suggested that users ensure that all parts of the distributed system are using the same ROS version and the same RMW implementation.