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

* Cross-Vendor communication is not guaranteed by design. Signed-off-by: Tomoya.Fujita <[email protected]> (cherry picked from commit 355ed2c) Co-authored-by: Tomoya Fujita <[email protected]>
ros2 · Sep 23, 2024 · 128440d · 128440d
1 parent eb4c86d
commit 128440d
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst b/source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst
@@ -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.