| 
    RTI Connext .Net APIs
    Version 5.3.1
    
   | 
 
Specifies and configures the mechanism that allows DDS::DataReader entities to detect when DDS::DataWriter entities become disconnected or "dead.". More...
Classes | |
| struct | DDS::LivelinessQosPolicy | 
| Specifies and configures the mechanism that allows DDS::DataReader entities to detect when DDS::DataWriter entities become disconnected or "dead.".  More... | |
Enumerations | |
| enum | DDS::LivelinessQosPolicyKind : UINT32 {  DDS::LivelinessQosPolicyKind::AUTOMATIC_LIVELINESS_QOS, DDS::LivelinessQosPolicyKind::MANUAL_BY_PARTICIPANT_LIVELINESS_QOS, DDS::LivelinessQosPolicyKind::MANUAL_BY_TOPIC_LIVELINESS_QOS }  | 
| Kinds of liveliness.  More... | |
Functions | |
| static System::String ^ | DDS::LivelinessQosPolicy::get_livelines_qos_policy_name () | 
| Stringified human-readable name for DDS::LivelinessQosPolicy.  More... | |
Specifies and configures the mechanism that allows DDS::DataReader entities to detect when DDS::DataWriter entities become disconnected or "dead.".
      
  | 
  strong | 
Kinds of liveliness.
| Enumerator | |
|---|---|
| AUTOMATIC_LIVELINESS_QOS | [default] The infrastructure will automatically signal liveliness for the DDS::DataWriter (s) at least as often as required by the DDS::DataWriter (S)  A DDS::DataWriter with this setting does not need to take any specific action in order to be considered 'alive.' The DDS::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.  | 
| MANUAL_BY_PARTICIPANT_LIVELINESS_QOS | RTI Connext will assume that as long as at least one DDS::DataWriter belonging to the DDS::DomainParticipant (or the DDS::DomainParticipant itself) has asserted its liveliness, then the other DataWriters belonging to that same DDS::DomainParticipant are also alive. The user application takes responsibility to signal liveliness to RTI Connext either by calling DDS::DomainParticipant::assert_liveliness, or by calling DDS::DataWriter::assert_liveliness, or DDS::TypedDataWriter::write on any DDS::DataWriter belonging to the DDS::DomainParticipant.  | 
| MANUAL_BY_TOPIC_LIVELINESS_QOS | RTI Connext will only assume liveliness of the DDS::DataWriter if the application has asserted liveliness of that DDS::DataWriter itself. The user application takes responsibility to signal liveliness to RTI Connext using the DDS::DataWriter::assert_liveliness method, or by writing some data.  | 
      
  | 
  inlinestatic | 
Stringified human-readable name for DDS::LivelinessQosPolicy.