This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
ddsf:public:guidebook:06_append:02_quality_of_service:liveliness [2021/07/14 15:53] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:02_quality_of_service:liveliness [2021/07/14 15:54] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[ddsf:public:guidebook:06_append:02_quality_of_service:start|return to the Quality of Service (QoS) Parameters ]] | [[ddsf:public:guidebook:06_append:02_quality_of_service:start|return to the Quality of Service (QoS) Parameters ]] | ||
| - | The [[ddsf:public:guidebook:06_append: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 [[ddsf:public:guidebook:06_append:glossary:i:instance|instance]], as determined by the [[ddsf:public:guidebook:06_append:glossary:o:ownership_qos|OWNERSHIP]] [[ddsf:private:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policy. | + | The [[ddsf:public:guidebook:06_append: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 [[ddsf:public:guidebook:06_append:glossary:i:instance|instance]], as determined by the [[ddsf:public:guidebook:06_append:glossary:o:ownership_qos|OWNERSHIP]] [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|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. | ||