Application Design

Defining Topic names in source code in each application is readable in example code, but is not ideal for a real system.

When you write keyed data, the RTI Connext DDS has to send the unique identifier of each instance along with the data.

You have two options for how to access data that a DataReader receives.

You should never block in a listener callback.  There are many negative consequences of blocking in a listener callback:

A DDS Publisher and Subscriber are responsible for sending and receiving the data. A Publisher contains one or multiple DataWriters.

When using a WaitSet, you can be notified of new data arriving two ways:

An application has multiple ways to be notified about data becoming available in a DataReader, depending on the application’s requirements - between these options, WaitSets are the safest.

To send or receive samples from the DDS dataspace or domain, you must create a domain participant in that domain.

Unlike when creating a socket and sending a UDP packet, creating DDS entities is more heavyweight.