<<spec>> Stores (name, value) pairs that can be used to determine access permissions. More...
Public Attributes | |
| final TagSeq | tags = new TagSeq() |
| <<spec>> Sequence of data tags. More... | |
 Public Attributes inherited from QosPolicy | |
| final QosPolicyId_t | id |
| The ID of this QoS policy. More... | |
| final String | policy_name |
| The name of this QoS policy. More... | |
Detailed Description
<<spec>> Stores (name, value) pairs that can be used to determine access permissions.
- Properties:
- RxO = N/A;
Changeable = NO
Usage
The DATA_TAG QoS policy can be used to associate a set of tags in the form of (name, value) pairs with a com.rti.dds.subscription.DataReader or com.rti.dds.publication.DataWriter. This is similar to the com.rti.dds.infrastructure.PropertyQosPolicy, except for the following differences:
- Data tags are always propagated. You cannot select whether or not a particular pair should be propagated.
- Data tags are not exposed to API functions, such as com.rti.dds.publication.DataWriter.get_matched_subscription_data, that receive com.rti.dds.publication.builtin.PublicationBuiltinTopicData or com.rti.dds.subscription.builtin.SubscriptionBuiltinTopicData as a parameter.
- Connext passes data tags to the Access Control Security Plugin, which may use them to decide whether to allow or deny the corresponding entities.
There are helper functions to facilitate working with data tags. See the DATA_TAG page.
Member Data Documentation
◆ tags
<<spec>> Sequence of data tags.
[default] An empty list.
- Categories
- Immutable, Discovery Metadata, Security
Referenced by DataTagQosPolicyHelper.add_tag(), DataTagQosPolicyHelper.assert_tag(), DataTagQosPolicyHelper.get_number_of_tags(), DataTagQosPolicyHelper.lookup_tag(), and DataTagQosPolicyHelper.remove_tag().