RTI Connext Java API Version 7.1.0
|
Stores name/value(string) pairs that can be used to configure certain parameters of RTI Connext that are not exposed through formal QoS policies. Can also be used to store and propagate application-specific name/value pairs that can be retrieved by user code during discovery. More...
Public Attributes | |
final PropertySeq | value |
Sequence of properties. More... | |
![]() | |
final QosPolicyId_t | id |
The ID of this QoS policy. More... | |
final String | policy_name |
The name of this QoS policy. More... | |
Stores name/value(string) pairs that can be used to configure certain parameters of RTI Connext that are not exposed through formal QoS policies. Can also be used to store and propagate application-specific name/value pairs that can be retrieved by user code during discovery.
The PROPERTY QoS policy can be used to associate a set of properties in the form of (name, value) pairs with a com.rti.dds.subscription.DataReader, com.rti.dds.publication.DataWriter, or com.rti.dds.domain.DomainParticipant. This is similar to the com.rti.dds.infrastructure.UserDataQosPolicy, except this policy uses (name, value) pairs, and you can select whether or not a particular pair should be propagated (included in the builtin topic).
This QoS policy may be used to configure:
In addition, you may add your own name/value pairs to the Property QoS policy of an Entity. Via this QoS policy, you can direct RTI Connext to propagate these name/value pairs with the discovery information for the Entity. Applications that discover the Entity can then access the user-specific name/value pairs in the discovery information of the remote Entity. This allows you to add meta-information about an Entity for application-specific use, for example, authentication/authorization certificates (which can also be done using the com.rti.dds.infrastructure.UserDataQosPolicy or com.rti.dds.infrastructure.GroupDataQosPolicy).
Some of the RTI Connext capabilities configurable via the Property QoS policy can also be configured in code via APIs. However, the Property QoS policy allows you to configure those parameters via XML files. In addition, some of the configuration APIs will only work if the Entity was created in a disabled state and then enabled after the configuration change was applied. By configuring those parameters using the Property QoS policy during entity creation, you avoid the additional work of first creating a disabled entity and then enabling it afterwards.
There are helper functions to facilitate working with properties, see the PROPERTY page.
final PropertySeq value |
Sequence of properties.
[default] An empty list.
Referenced by PropertyQosPolicyHelper.add_property(), PropertyQosPolicyHelper.assert_property(), PropertyQosPolicyHelper.get_number_of_properties(), PropertyQosPolicyHelper.get_properties(), PropertyQosPolicyHelper.get_qos_resource_limits_property_string_max_length(), PropertyQosPolicyHelper.lookup_property(), and PropertyQosPolicyHelper.remove_property().