When you use RTI Connector, all the types, topics, domain, and entities must be defined in an XML file that gets loaded when the Connector object is created.

For example, the following snippet loads the required definitions from "config.xml" and then instantiates a new Connector object for the domain participant "MyParticipant" defined in the participant library "MyParticipantLib"

const rti = require('rticonnextdds-connector');
var connector = new rti.Connector("MyParticipantLib::MyParticipant", "config.xml");


857 reads — 0 comments
Topic Queries introduce another way for DDS developers to intelligently access data within their systems. This is a new feature introduced in Connext 5.3 that complements Content Filtered Topics and the Durability Qos policy. Content filtered topics (CFTs) allow a DataReader to subscribe to a
1025 reads — 0 comments
QoS (Quality of Service) in DDS (Data Distribution Service) are a set of configurable parameters that control the behavior of a DDS system, such as resource consumption, fault tolerance, and communication reliability. Each entity (Topic, DataReader, DataWriter, Publisher, Subscriber, and
13225 reads — 2 comments
DDS (Data Distribution Service) is a specification for publish-subscribe data-distribution systems. The purpose of the specification is to provide a common application-level interface that clearly defines the data distribution service. The specification describes the service using UML, thus
8322 reads — 0 comments
The purpose of this document is to describe how to use Eclipse to develop C/C++ Connext DDS applications. We will create a simple DDS application using rtiddsgen, set up and Eclipse project to build the application, and finally run it within the IDE.
13930 reads — 1 comment
This HOWTO applies to the "classic" C and C++ API to the OMG Data Distribution Service (DDS) in which the data-types used to hold sequences were defined as specialized containers. This is needed for C and in the case of C++ was done to comply with IDL to language mappings that proceeded the use of the standard template library.
15242 reads — 0 comments
There are various strategies that can be used to have DDS applications communicate between each other despite the fact that one or more of these applications are protected by a firewall. This HOWTO focuses in the situation where there is a desire to use static configuration (i.e. manually open specific ports or multicast addresses in the firewall) and the applications are protected with Firewalls but are not behind Network Address Translators (NATs).
16633 reads — 1 comment
Subscribe to RSS - DDS