RTI Connext Java API  Version 5.0.0
GroupDataQosPolicy Class Reference

Attaches a buffer of opaque data that is distributed by means of Built-in Topics during discovery. More...

Inheritance diagram for GroupDataQosPolicy:

Public Attributes

final ByteSeq value
 a sequence of octets
- Public Attributes inherited from QosPolicy
final QosPolicyId_t id
 The ID of this QoS policy.
final String policy_name
 The name of this QoS policy.

Additional Inherited Members

- Public Member Functions inherited from Struct
abstract boolean equals (Object obj)
abstract int hashCode ()
String toString ()
- Protected Member Functions inherited from Struct
 Struct ()
abstract void pull_from_nativeI (long native_status)
abstract void push_to_nativeI (long native_status)

Detailed Description

Attaches a buffer of opaque data that is distributed by means of Built-in Topics during discovery.

com.rti.dds.publication.Publisher, com.rti.dds.subscription.Subscriber
RxO = NO
Changeable = YES
See Also


The additional information is attached to a com.rti.dds.publication.Publisher or com.rti.dds.subscription.Subscriber. This extra data is not used by RTI Connext itself. When a remote application discovers the com.rti.dds.publication.Publisher or com.rti.dds.subscription.Subscriber, it can access that information and use it for its own purposes.

Use cases for this QoS policy, as well as the com.rti.dds.infrastructure.TopicDataQosPolicy and com.rti.dds.infrastructure.UserDataQosPolicy, are often application-to-application identification, authentication, authorization, and encryption purposes. For example, applications can use Group or User Data to send security certificates to each other for RSA-type security.

In combination with com.rti.dds.subscription.DataReaderListener, com.rti.dds.publication.DataWriterListener and operations such as com.rti.dds.domain.DomainParticipant.ignore_publication and com.rti.dds.domain.DomainParticipant.ignore_subscription, this QoS policy can help an application to define and enforce its own security policies. For example, an application can implement matching policies similar to those of the com.rti.dds.infrastructure.PartitionQosPolicy, except the decision can be made based on an application-defined policy.

The use of this QoS is not limited to security; it offers a simple, yet flexible extensibility mechanism.

Important: RTI Connext stores the data placed in this policy in pre-allocated pools. It is therefore necessary to configure RTI Connext with the maximum size of the data that will be stored in policies of this type. This size is configured with com.rti.dds.infrastructure.DomainParticipantResourceLimitsQosPolicy.publisher_group_data_max_length and com.rti.dds.infrastructure.DomainParticipantResourceLimitsQosPolicy.subscriber_group_data_max_length.

Member Data Documentation

final ByteSeq value

a sequence of octets

[default] Empty (zero-sized)

[range] Octet sequence of length [0,max_length]

RTI Connext Java API Version 5.0.0 Copyright © Thu Aug 30 2012 Real-Time Innovations, Inc