rmw
master
C API providing a middleware abstraction layer which is used to implement the rest of ROS.
|
#include <types.h>
Public Attributes | |
enum rmw_qos_history_policy_t | history |
size_t | depth |
enum rmw_qos_reliability_policy_t | reliability |
enum rmw_qos_durability_policy_t | durability |
bool | avoid_ros_namespace_conventions |
If true, any ROS specific namespacing conventions will be circumvented. More... | |
enum rmw_qos_history_policy_t rmw_qos_profile_t::history |
size_t rmw_qos_profile_t::depth |
enum rmw_qos_reliability_policy_t rmw_qos_profile_t::reliability |
enum rmw_qos_durability_policy_t rmw_qos_profile_t::durability |
bool rmw_qos_profile_t::avoid_ros_namespace_conventions |
If true, any ROS specific namespacing conventions will be circumvented.
In the case of DDS and topics, for example, this means the typical ROS specific prefix of rt
would not be applied as described here:
http://design.ros2.org/articles/topic_and_service_names.html#ros-specific-namespace-prefix
This might be useful when trying to directly connect a native DDS topic with a ROS 2 topic.