RTI Core Libraries and Utilities

Note : Applies to RTI Connext 5.2.x and above. When you run an RTI Connext DDS host installer, the installation directory will always be like this: <default install path or user defined installation path>/rti_connext_dds-x.x.x . The installer itself adds the “ rti_connext_dds-x.x.x ”. If you ...
68 reads — 0 comments
QoS configurations for transport when starting applications with network interfaces disabled for IP mobility use case With the introduction of version 5.3.0, Connext DDS supports Locator change at runtime. The IP mobility feature allows DDS applications to start without enabled network interfaces. ...
517 reads — 0 comments
RTI Connext DDS assigns a number, called a GUID, to each entity in order to uniquely identify it for the discovery process to work correctly. You can control how to set the GUID using the value assigned to rtps_auto_id_kind . For more information, see 8.5.9.4 Controlling How the GUID is Set ( ...
862 reads — 0 comments
RTI Connext DDS uses a special discovery mechanism that allows RTI Tools such as Admin Console to find participants on different domains. The messages that make this possible are called default domain announcements. RTI Connext provides a couple of QoS settings that allow this special discovery ...
688 reads — 0 comments
This article assumes familiarity with Docker. For instance, you should know the difference between containers and images, and the purpose of a Dockerfile. If not, visit www.docker.com and get up to speed on Docker basics before reading further. Introduction In this example, we’ll build and deploy a ...
1073 reads — 0 comments
This article assumes familiarity with Docker. For instance, you should know the difference between containers and images, and the purpose of a Dockerfile. If not, then visit www.docker.com and get up to speed on Docker basics before reading further. Introduction In this example, we’ll create a ...
1031 reads — 0 comments
When using the “host” Docker driver, all network interfaces of the host machine are accessible from the Docker container. Furthermore, there is no networking namespace separation between the Docker containers and the host machine. To run a container in host mode, run the following command: $ docker ...
1304 reads — 0 comments
Multicast over UDPv4 can be used for data transfer between applications that are running on the same machine, even if shared memory is enabled. RTI's Connext DDS provides various transports, which can be configured using the USER_QOS_PROFILES.xml file. The most commonly used transports are shared ...
623 reads — 0 comments
Introduction Docker enables containers to communicate with one another and with the host machine using Interprocess communication (IPC). As explained in the Docker’s documentation: IPC (POSIX/SysV IPC) namespace provides separation of named shared memory segments, semaphores and message queues. ...
1542 reads — 0 comments
RTI Connext DDS allows you to use different transports for communication between endpoints in your application (e.g., shared memory, UDP, TCP, etc.). You can take advantage of this flexibility and use different transports for discovery data and user data in the same application. This article shows ...
1608 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities