#include <managed_infrastructure.h>
Public Attributes | |
Duration_t | min_heartbeat_response_delay |
The minimum delay to respond to a heartbeat. | |
Duration_t | max_heartbeat_response_delay |
The maximum delay to respond to a heartbeat. | |
Duration_t | heartbeat_suppression_duration |
The duration a reader ignores consecutively received heartbeats. | |
Duration_t | nack_period |
The period at which to send NACKs. |
It is used to config reliable reader according to RTPS protocol.
The minimum delay to respond to a heartbeat.
When a reliable reader receives a heartbeat from a remote writer and finds out that it needs to send back an ACK/NACK message, the reader can choose to delay a while. This sets the value of the minimum delay.
[default] 0 seconds
[range] [0, 1 year], <= max_heartbeat_response_delay
The maximum delay to respond to a heartbeat.
When a reliable reader receives a heartbeat from a remote writer and finds out that it needs to send back an ACK/NACK message, the reader can choose to delay a while. This sets the value of maximum delay.
[default] The default value depends on the container policy:
For DDS::DiscoveryConfigQosPolicy : 0 seconds
For DDS::DataReaderProtocolQosPolicy : 0.5 seconds
[range] [0, 1 year], >= min_heartbeat_response_delay
The duration a reader ignores consecutively received heartbeats.
When a reliable reader receives consecutive heartbeats within a short duration that will trigger redundant NACKs, the reader may ignore the latter heartbeat(s). This sets the duration during which additionally received heartbeats are suppressed.
[default] 0.0625 seconds
[range] [0, 1 year],
The period at which to send NACKs.
A reliable reader will send periodic NACKs at this rate when it first matches with a reliable writer. The reader will stop sending NACKs when it has received all available historical data from the writer.
[default] 5 seconds
[range] [1 nanosec, 1 year]