From 128440db8058494d6ac33276e0e14e0ce910e170 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Mon, 23 Sep 2024 11:13:00 +0900 Subject: [PATCH] Cross-Vendor communication is not guaranteed by design. (#4736) (#4769) * Cross-Vendor communication is not guaranteed by design. Signed-off-by: Tomoya.Fujita (cherry picked from commit 355ed2c470be2cd185eea5a6f44164f7697e0cae) Co-authored-by: Tomoya Fujita --- .../Intermediate/About-Different-Middleware-Vendors.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst b/source/Concepts/Intermediate/About-Different-Middleware-Vendors.rst index dc8d1d897d..8c1b9ae433 100644 --- 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.