Usually DataReaders receive data in the order that it was sent by a DataWriter. In addition, data is presented to the DataReader as soon as the application receives the next value expected. In this example we illustrate how to control the scope of the order in which samples are presented to the subscribing application.
The Multichannel QoS policy is used to partition the data published by a DataWriter across multiple channels. This example shows how to use multichannel DataWriters.
This example shows how to publish and subscribe Shapes using the Dynamic Data API. In particular, we create a publisher and a subscriber application that operate on the "Square" through Dynamic Data calls.
This example shows how to create a simple adapter using the RTI Routing Service Adapter SDK. The adapter scans the file system in one specific folder and, for every file present in that folder, it creates a stream to communicate with the output. In the output, the adapter will take care of creating a file for every stream received.
This example shows how to configure a datawriter for asynchronous publication. This means that instead of sending a sample before returning from write(), the data is enqueued and sent according to a flow controller.
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.
