LivelinessQosPolicyKind Class Reference
[LIVELINESS]

Kinds of liveliness. More...

Inheritance diagram for LivelinessQosPolicyKind:

List of all members.

Static Public Attributes
static final LivelinessQosPolicyKind	AUTOMATIC_LIVELINESS_QOS
	[default] The infrastructure will automatically signal liveliness for the com.rti.dds.publication.DataWriter (s) at least as often as required by the lease_duration.
static final LivelinessQosPolicyKind	MANUAL_BY_PARTICIPANT_LIVELINESS_QOS
	RTI Connext will assume that as long as at least one com.rti.dds.publication.DataWriter belonging to the com.rti.dds.domain.DomainParticipant (or the com.rti.dds.domain.DomainParticipant itself) has asserted its liveliness, then the other Entities belonging to that same com.rti.dds.domain.DomainParticipant are also alive.
static final LivelinessQosPolicyKind	MANUAL_BY_TOPIC_LIVELINESS_QOS
	RTI Connext will only assume liveliness of the com.rti.dds.publication.DataWriter if the application has asserted liveliness of that com.rti.dds.publication.DataWriter itself.

---

Detailed Description

Kinds of liveliness.

QoS:

com.rti.dds.infrastructure.LivelinessQosPolicy

---

Member Data Documentation

final LivelinessQosPolicyKind AUTOMATIC_LIVELINESS_QOS [static]

[default] The infrastructure will automatically signal liveliness for the com.rti.dds.publication.DataWriter (s) at least as often as required by the lease_duration.

A com.rti.dds.publication.DataWriter with this setting does not need to take any specific action in order to be considered 'alive.' The com.rti.dds.publication.DataWriter is only 'not alive' when the participant to which it belongs terminates (gracefully or not), or when there is a network problem that prevents the current participant from contacting that remote participant.

final LivelinessQosPolicyKind MANUAL_BY_PARTICIPANT_LIVELINESS_QOS [static]

RTI Connext will assume that as long as at least one com.rti.dds.publication.DataWriter belonging to the com.rti.dds.domain.DomainParticipant (or the com.rti.dds.domain.DomainParticipant itself) has asserted its liveliness, then the other Entities belonging to that same com.rti.dds.domain.DomainParticipant are also alive.

The user application takes responsibility to signal liveliness to RTI Connext either by calling com.rti.dds.domain.DomainParticipant.assert_liveliness, or by calling com.rti.dds.publication.DataWriter.assert_liveliness, or com.rti.dds.topic.example.FooDataWriter.write on any com.rti.dds.publication.DataWriter belonging to the com.rti.dds.domain.DomainParticipant.

final LivelinessQosPolicyKind MANUAL_BY_TOPIC_LIVELINESS_QOS [static]

RTI Connext will only assume liveliness of the com.rti.dds.publication.DataWriter if the application has asserted liveliness of that com.rti.dds.publication.DataWriter itself.

The user application takes responsibility to signal liveliness to RTI Connext using the com.rti.dds.publication.DataWriter.assert_liveliness method, or by writing some data.