rmw  master
C API providing a middleware abstraction layer which is used to implement the rest of ROS.
Public Attributes | List of all members
rmw_qos_profile_t Struct Reference

ROS MiddleWare quality of service profile. More...

#include <types.h>

Public Attributes

enum rmw_qos_history_policy_t history
 
size_t depth
 Size of the message queue. More...
 
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...
 

Detailed Description

ROS MiddleWare quality of service profile.

Member Data Documentation

◆ history

enum rmw_qos_history_policy_t rmw_qos_profile_t::history

◆ depth

size_t rmw_qos_profile_t::depth

Size of the message queue.

◆ reliability

enum rmw_qos_reliability_policy_t rmw_qos_profile_t::reliability

◆ durability

enum rmw_qos_durability_policy_t rmw_qos_profile_t::durability

◆ avoid_ros_namespace_conventions

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.


The documentation for this struct was generated from the following file: