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 |
| Reliabiilty QoS policy setting. More... | |
| enum rmw_qos_durability_policy_t | durability |
| Durability QoS policy setting. More... | |
| struct rmw_time_t | deadline |
| The period at which messages are expected to be sent/received. More... | |
| struct rmw_time_t | lifespan |
| The age at which messages are considered expired and no longer valid. More... | |
| enum rmw_qos_liveliness_policy_t | liveliness |
| Liveliness QoS policy setting. More... | |
| struct rmw_time_t | liveliness_lease_duration |
| The time within which the RMW node or publisher must show that it is alive. More... | |
| 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 |
Reliabiilty QoS policy setting.
◆ durability
| enum rmw_qos_durability_policy_t rmw_qos_profile_t::durability |
Durability QoS policy setting.
◆ deadline
| struct rmw_time_t rmw_qos_profile_t::deadline |
The period at which messages are expected to be sent/received.
◆ lifespan
| struct rmw_time_t rmw_qos_profile_t::lifespan |
The age at which messages are considered expired and no longer valid.
◆ liveliness
| enum rmw_qos_liveliness_policy_t rmw_qos_profile_t::liveliness |
Liveliness QoS policy setting.
◆ liveliness_lease_duration
| struct rmw_time_t rmw_qos_profile_t::liveliness_lease_duration |
The time within which the RMW node or publisher must show that it is alive.
◆ 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:
- include/rmw/types.h
