This example shows how to define listeners for different entity classes (i.e., DomainParticipant, Topic, Publisher, DataWriter, Subscriber, and DataReader), adding methods for handling entity-specific statuses.
The Property QosPolicy is used to specify name/value pairs of data and attach them to an entity. This example shows how to use the Property QosPolicy to modify the send and receive socket buffer transport properties.
This second example on Keyed Data shows how the Ownership QoS interacts with the registration, unregistration, and disposal of instance of multiple DataWriters. It also illustrates how the on_data_available callback on the DataReader can delegate to ther handlers based on instance state changes, and explains filtering mechanisms to read only certain keys.
Built-in Topics allow us to access some relevant information about Connext DDS entities, such as the access to application specific data in discovery. This example shows how USER_DATA QoS for security during discovery phase.
This example shows the combined use of Content Filters with the Deadline QoS, which specifies the updates you expect for a particular instance within a given period of time.
In this example we illustrate how to use the Partition QoS, which provides a way to control which DataWriters will match—and thus communicate with—which Data Writers.
This example illustrate how to use keyed data. In particular, in this example a single DataWriter creates three instances differentiated by the field "code", which is the field used as key.
Connext uses the discriminator field of the struct to decide what field in the struct is actually sent on the wire. In this example we illustrate how to access the discriminator of a Union using the Dynamic Data API.
