![\](ftv2mlastnode.png) com | |
![](ftv2blank.png) ![\](ftv2mlastnode.png) rti | RTI |
![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2mnode.png) connext | RTI Connext Messaging communication patterns |
![](ftv2blank.png) ![](ftv2blank.png) ![|](ftv2vertline.png) ![\](ftv2lastnode.png) requestreply | Support for the request-reply communication pattern |
![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2mnode.png) ndds | Unsupported APIs used by examples in the RTI Connext distribution as well as in rtiddsgen-generated examples |
![](ftv2blank.png) ![](ftv2blank.png) ![|](ftv2vertline.png) ![o](ftv2node.png) example | Programming HowTos: Code templates for common use cases |
![](ftv2blank.png) ![](ftv2blank.png) ![|](ftv2vertline.png) ![o](ftv2node.png) config | Utility API's independent of the DDS standard |
![](ftv2blank.png) ![](ftv2blank.png) ![|](ftv2vertline.png) ![\](ftv2lastnode.png) transport | APIs related to RTI Connext pluggable transports |
![](ftv2blank.png) ![](ftv2blank.png) ![\](ftv2mlastnode.png) dds | DDS |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) domain | Contains the com.rti.dds.domain.DomainParticipant class that acts as an entrypoint of RTI Connext and acts as a factory for many of the classes. The com.rti.dds.domain.DomainParticipant also acts as a container for the other objects that make up RTI Connext |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) dynamicdata | <<extension>> The Dynamic Data API provides a way to interact with arbitrarily complex data types at runtime without the need for code generation |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) infrastructure | Defines the abstract classes and the interfaces that are refined by the other modules. Contains common definitions such as return codes, status values, and QoS policies |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) publication | Contains the com.rti.dds.publication.FlowController, com.rti.dds.publication.Publisher, and com.rti.dds.publication.DataWriter classes as well as the com.rti.dds.publication.PublisherListener and com.rti.dds.publication.DataWriterListener interfaces, and more generally, all that is needed on the publication side |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) subscription | Contains the com.rti.dds.subscription.Subscriber, com.rti.dds.subscription.DataReader, com.rti.dds.subscription.ReadCondition, com.rti.dds.subscription.QueryCondition, and com.rti.dds.subscription.TopicQuery classes, as well as the com.rti.dds.subscription.SubscriberListener and com.rti.dds.subscription.DataReaderListener interfaces, and more generally, all that is needed on the subscription side |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) topic | Contains the com.rti.dds.topic.Topic, com.rti.dds.topic.ContentFilteredTopic, and com.rti.dds.topic.MultiTopic classes, the com.rti.dds.topic.TopicListener interface, and more generally, all that is needed by an application to define com.rti.dds.topic.Topic objects and attach QoS policies to them |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2mnode.png) type | |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![|](ftv2vertline.png) ![\](ftv2lastnode.png) builtin | RTI Connext provides a set of very simple data types for you to use with the topics in your application |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![o](ftv2node.png) typecode | <<extension>> A com.rti.dds.typecode.TypeCode is a mechanism for representing a type at runtime. RTI Connext can use type codes to send type definitions on the network. You will need to understand this API in order to use the Dynamic Data capability or to inspect the type information you receive from remote readers and writers |
![](ftv2blank.png) ![](ftv2blank.png) ![](ftv2blank.png) ![\](ftv2lastnode.png) util | Utility types that support the DDS API |