RTI Connext Traditional C++ API  Version 5.2.3
 All Classes Functions Variables Typedefs Enumerations Enumerator Groups Pages
Here is a list of all modules:
[detail level 12345]
oDocumentation Roadmap
oUsing DDS:: Namespace
oRTI Connext DDS API ReferenceRTI Connext modules following the DDS module definitions
|oDomain ModuleContains the DDSDomainParticipant class that acts as an entrypoint of RTI Connext and acts as a factory for many of the classes. The DDSDomainParticipant also acts as a container for the other objects that make up RTI Connext
||oDomainParticipantFactoryDDSDomainParticipantFactory entity and associated elements
||oDomainParticipantsDDSDomainParticipant entity and associated elements
||\Built-in TopicsBuilt-in objects created by RTI Connext but accessible to the application
|oTopic ModuleContains the DDSTopic, DDSContentFilteredTopic, and DDSMultiTopic classes, the DDSTopicListener interface, and more generally, all that is needed by an application to define DDSTopic objects and attach QoS policies to them
||oTopicsDDSTopic entity and associated elements
||oUser Data Type SupportDefines generic classes and macros to support user data types
||oType Code Support<<extension>> A DDS_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
||oBuilt-in TypesRTI Connext provides a set of very simple data types for you to use with the topics in your application
||oDynamic Data<<extension>> The Dynamic Data API provides a way to interact with arbitrarily complex data types at runtime without the need for code generation
||\DDS-Specific Primitive TypesBasic DDS value types for use in user data types
|oPublication ModuleContains the DDSFlowController, DDSPublisher, and DDSDataWriter classes as well as the DDSPublisherListener and DDSDataWriterListener interfaces, and more generally, all that is needed on the publication side
||oPublishersDDSPublisher entity and associated elements
||oData WritersDDSDataWriter entity and associated elements
||oFlow Controllers<<extension>> DDSFlowController and associated elements
||\Multi-channel DataWritersAPIs related to Multi-channel DataWriters
|oSubscription ModuleContains the DDSSubscriber, DDSDataReader, DDSReadCondition, and DDSQueryCondition classes, as well as the DDSSubscriberListener and DDSDataReaderListener interfaces, and more generally, all that is needed on the subscription side
||oSubscribersDDSSubscriber entity and associated elements
||oDataReadersDDSDataReader entity and associated elements
||\Data SamplesDDS_SampleInfo, DDS_SampleStateKind, DDS_ViewStateKind, DDS_InstanceStateKind and associated elements
|oInfrastructure ModuleDefines 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
||oClock SelectionAPIs related to clock selection
||oTime SupportTime and duration types and defines
||oGUID Support<<extension>> GUID type and defines
||oSequence Number Support<<extension>> Sequence number type and defines
||oException Codes<<extension>> Exception codes
||oReturn CodesTypes of return codes
||oStatus KindsKinds of communication status
||oQoS PoliciesQuality of Service (QoS) policies
||oEntity SupportDDSEntity, DDSListener and related items
||oConditions and WaitSetsDDSCondition and DDSWaitSet and related items
||oCookie<<extension>> Unique identifier for a written data sample
||oSample Flags<<extension>> Flags for samples
||oHeap Support<<extension>> Heap allocation and free routines
||oBuiltin Qos Profiles<<extension>> QoS libraries and profiles that are automatically built into RTI Connext
||oUser-managed ThreadsUser-managed thread infrastructure
||oOctet Buffer Support<<extension>> Octet buffer creation, cloning, and deletion
||oSequence SupportThe FooSeq interface allows you to work with variable-length collections of homogeneous data
||\String Support<<extension>> String creation, cloning, assignment, and deletion
|oPluggable TransportsAPIs related to RTI Connext pluggable transports
||oUsing Transport PluginsConfiguring transports used by RTI Connext
||oBuilt-in Transport PluginsTransport plugins delivered with RTI Connext
||oClass IdTransport class ID. Specifies the ID of a Transport-Plugin 'class'
||oAddressTransport-independent addressing scheme using IPv6 presentation strings and numerically stored in network-ordered format
||\AttributesBase "class" of the properties of any Transport Plugin
|oQueries and Filters Syntax
|oConfiguration UtilitiesUtility API's independent of the DDS standard
|oUnsupported UtilitiesUnsupported APIs used by examples in the RTI Connext distribution as well as in rtiddsgen-generated examples
|oDurability and PersistenceAPIs related to RTI Connext Durability and Persistence
|oSystem PropertiesSystem Properties
|oConfiguring QoS Profiles with XMLAPIs related to XML QoS Profiles
|\RTI Connext Messaging API ReferenceExtensions to the RTI Connext publish-subscribe functionality
| oRequest-Reply PatternSupport for the request-reply communication pattern
| oInfrastructureInfrastructure types for RTI Connext Messaging
| \Queuing PatternSupport for the queuing communication pattern
oProgramming How-To'sThese "How To"s illustrate how to apply RTI Connext APIs to common use cases
|oPublication ExampleA data publication example
|oSubscription ExampleA data subscription example
|oParticipant Use CasesWorking with domain partcipants
|oTopic Use CasesWorking with topics
|oFlowController Use CasesWorking with flow controllers
|oPublisher Use CasesWorking with publishers
|oDataWriter Use CasesWorking with data writers
|oSubscriber Use CasesWorking with subscribers
|oDataReader Use CasesWorking with data readers
|oEntity Use CasesWorking with entities
|oWaitset Use CasesUsing wait-sets and conditions
|oTransport Use CasesWorking with pluggable transports
|oFilter Use CasesWorking with data filters
|oCreating Custom Content FiltersWorking with custom content filters
|oLarge Data Use CasesWorking with large data types
|\Request-Reply ExamplesExamples on how to use the request-reply API
\Programming Tools
 ortiddsgenGenerates source code from data types declared in IDL or XML files
 ortiddspingSends or receives simple messages using RTI Connext
 \rtiddsspyDebugging tool which receives all RTI Connext communication

RTI Connext Traditional C++ API Version 5.2.3 Copyright © Wed Apr 27 2016 Real-Time Innovations, Inc