59.18 OWNERSHIP_STRENGTH QosPolicy
The OWNERSHIP_STRENGTH QosPolicy is used to rank DataWriters of the same instance of a Topic, so that Connext can decide which DataWriter will have ownership of the instance when the 59.17 OWNERSHIP QosPolicy is set to EXCLUSIVE.
It includes the member in Table 59.33 DDS_OwnershipStrengthQosPolicy.
See the API Reference HTML documentation for complete QoS details, including functional categories, defaults, and other QoS attributes. (API References are here: <NDDSHOME>/doc/api/connext_dds/api_<language>) For example,
|
Type |
Field Name |
Description |
|
DDS_Long |
value |
The strength value used to arbitrate among multiple DataWriters. |
This QosPolicy only applies to DataWriters when EXCLUSIVE OWNERSHIP is used. The strength is simply an integer value, and the DataWriter with the largest value is the owner. A deterministic method is used to decide which DataWriter is the owner when there are multiple DataWriters that have equal strengths. See 59.17.1 How Connext Selects which DataWriter is the Exclusive Owner for more details.
59.18.1 Example
Suppose there are two DataWriters sending DDS samples of the same Topic instance, one as the main DataWriter, and the other as a backup. If you want to make sure the DataReader always receive from the main one whenever possible, then set the main DataWriter to use a higher ownership_strength value than the one used by the backup DataWriter.
59.18.2 Properties
This QosPolicy can be changed at any time.
It does not apply to DataReaders, so there is no requirement that the publishing and subscribing sides use compatible values.
59.18.3 Related QosPolicies
59.18.4 Applicable Entities
59.18.5 System Resource Considerations
The use of this policy does not significantly impact the use of resources.