Application Design

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

4726 reads — 0 comments

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

3476 reads — 0 comments

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

2129 reads — 0 comments

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

5337 reads — 0 comments

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

4753 reads — 0 comments

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

2045 reads — 0 comments

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.

6665 reads — 2 comments

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

4171 reads — 0 comments

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

1756 reads — 0 comments
Subscribe to RSS - Application Design