DPSE_DiscoveryPluginProperty Struct Reference

<<eXtension>> <<cert>> Properties for the Dynamic Participant/Static Endpoint (DPSE) discovery plugin. This includes all discovery timing properties for participant discovery. More...

#include <disc_dpse_dpsediscovery.h>

Data Fields
struct DDS_Duration_t	participant_liveliness_assert_period
	The period to assert liveliness for the participant.
struct DDS_Duration_t	participant_liveliness_lease_duration
	The liveliness lease duration for the participant.
DDS_Long	initial_participant_announcements
	The number of initial announcements sent when a participant is first enabled or when a remote participant is newly discovered.
struct DDS_Duration_t	initial_participant_announcement_period
	The period between initial announcements when a participant is first enabled or when a remote participant is newly discovered.
DDS_Long	max_participant_locators
	The maximum number of locators RTI Connext DDS Micro can send to to discover other participants in the same domain.
DDS_Long	max_locators_per_discovered_participant
	The maximum number of locators RTI Connext DDS Micro can keep track of per discovered participant.
DDS_ReliabilityQosPolicyKind	participant_message_reader_reliability_kind
	Reliability policy for a built-in participant message reader.

---

Detailed Description

<<eXtension>> <<cert>> Properties for the Dynamic Participant/Static Endpoint (DPSE) discovery plugin. This includes all discovery timing properties for participant discovery.

---

Field Documentation

struct DDS_Duration_t DPSE_DiscoveryPluginProperty::participant_liveliness_assert_period

The period to assert liveliness for the participant.

Specifies how often the DomainParticipant's discovery DataWriter will assert the liveliness of the DomainParticipant to its peers.

Should be strictly less than participant_liveliness_lease_duration.

[default] 30 seconds

[range] [1 nanosec, 1 year], < participant_liveliness_lease_duration

struct DDS_Duration_t DPSE_DiscoveryPluginProperty::participant_liveliness_lease_duration

The liveliness lease duration for the participant.

This is the same as the expiration time of the DomainParticipant as defined in the RTPS protocol.

If the participant has not refreshed its own liveliness to other participants at least once within this period, it may be considered as stale by other participants in the network.

Should be strictly greater than participant_liveliness_assert_period.

[default] 100 seconds

[range] [1 nanosec, 1 year], > participant_liveliness_assert_period

DDS_Long DPSE_DiscoveryPluginProperty::initial_participant_announcements

The number of initial announcements sent when a participant is first enabled or when a remote participant is newly discovered.

The number of initial announcements sent when a participant is first enabled or when a remote participant is newly discovered.

Also, when a new remote participant appears, the local participant will announce itself to the peers a number of times controlled by this parameter.

[default] 5

struct DDS_Duration_t DPSE_DiscoveryPluginProperty::initial_participant_announcement_period

The period between initial announcements when a participant is first enabled or when a remote participant is newly discovered.

[default] 1 second

DDS_Long DPSE_DiscoveryPluginProperty::max_participant_locators

The maximum number of locators RTI Connext DDS Micro can send to to discover other participants in the same domain.

The discovery plugin sends participant annoucements to a number of locators as specified in the initial peer list. The maximum number of locators to send too is specified here.

The value DDS_LENGTH_AUTO calculates the maximum number of locators as DomainParticipantQos.resource_limits.remote_participant_allocation + (DPDE_MAX_ANON_PARTICIPANT * (initial_peers length + 1));

[default] DDS_LENGTH_AUTO;

DDS_Long DPSE_DiscoveryPluginProperty::max_locators_per_discovered_participant

The maximum number of locators RTI Connext DDS Micro can keep track of per discovered participant.

When a participant discover another participant, it must keep track of which addresses to respond to for each participant. NOTE: If two participants respond with the same addresses, for example multicast, only one address is saved.

[default] 4;

DDS_ReliabilityQosPolicyKind DPSE_DiscoveryPluginProperty::participant_message_reader_reliability_kind

Reliability policy for a built-in participant message reader.

For details, refer to the DDS_ReliabilityQosPolicyKind.

[default] DDS_BEST_EFFORT_RELIABILITY_QOS