dido:public:ra:xapend:xapend.f_qos:11_liveliness
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.f_qos:11_liveliness [2021/06/06 15:53] char ↷ Page name changed from dido:public:ra:xapend:xapend.f_qos:liveliness to dido:public:ra:xapend:xapend.f_qos:11_liveliness |
dido:public:ra:xapend:xapend.f_qos:11_liveliness [2021/10/04 13:40] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Liveliness ====== | + | ====== F.11 Liveliness ====== |
| - | [[dido:public:ra:xapend:xapend.f_qos| Return to Quality of Service ]] | + | [[dido:public:ra:xapend:xapend.f_qos:start| Return to DDS Quality of Service ]] |
| - | The [[dido:public:ra:xapend:xapend.glossary:l:liveliness_qos|LIVELINESS]] policy controls the mechanism and parameters used by the Service to ensure that particular entities on the network are still “alive.” The liveliness can also affect the ownership of a particular [[dido:public:ra:xapend:xapend.glossary:i:instance|instance]], as determined by the [[dido:public:ra:xapend:xapend.glossary:o:ownership_qos|OWNERSHIP]] [[dido:public:ra:xapend:xapend.a_glossary:q:qos|QoS]] policy. | + | The [[dido:public:ra:xapend:xapend.a_glossary:l:liveliness_qos|LIVELINESS]] [[dido:public:ra:xapend:xapend.a_glossary:p:policy|policy]] controls the mechanism and parameters used by the Service to ensure that particular entities on the network are still “alive.” The liveliness can also affect the ownership of a particular [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]], as determined by the [[dido:public:ra:xapend:xapend.a_glossary:o:ownership_qos|OWNERSHIP QoS]] policy. |
| This policy has several settings to support both data-objects that are updated periodically as well as those that are changed sporadically. It also allows customizing for different application requirements in terms of the kinds of failures that will be detected by the liveliness mechanism. | This policy has several settings to support both data-objects that are updated periodically as well as those that are changed sporadically. It also allows customizing for different application requirements in terms of the kinds of failures that will be detected by the liveliness mechanism. | ||
| - | The AUTOMATIC liveliness setting is most appropriate for applications that only need to detect failures at the processlevel, but not application-logic failures within a process. The Service takes responsibility for renewing the leases at the required rates and thus, as long as the local process where a ''DomainParticipant'' is running and the link connecting it to remote participants remains connected, the entities within the ''DomainParticipant'' will be considered alive. This requires the lowest overhead. | + | The AUTOMATIC liveliness setting is most appropriate for [[dido:public:ra:xapend:xapend.a_glossary:a:application|applications]] that only need to detect failures at the processlevel, but not application-logic failures within a process. The Service takes responsibility for renewing the leases at the required rates and thus, as long as the local process where a ''DomainParticipant'' is running and the link connecting it to remote participants remains connected, the entities within the ''DomainParticipant'' will be considered alive. This requires the lowest overhead. |
| The MANUAL settings (MANUAL_BY_PARTICIPANT, MANUAL_BY_TOPIC), require the application on the publishing | The MANUAL settings (MANUAL_BY_PARTICIPANT, MANUAL_BY_TOPIC), require the application on the publishing | ||
| Line 24: | Line 24: | ||
| Source: [[https://www.omg.org/spec/DDS/1.4/PDF | DDS 1.4 Spec]] | Source: [[https://www.omg.org/spec/DDS/1.4/PDF | DDS 1.4 Spec]] | ||
| + | |||
dido/public/ra/xapend/xapend.f_qos/11_liveliness.1623009221.txt.gz · Last modified: 2021/06/06 15:53 by char
