4. Release Notes

4.1. Supported Platforms

This release of RTI Connext DDS Network Binding Library supports the following versions with Connext Drive :

Connext Professional 7.3.1
Connext Micro 2.4.14.3
Connext Cert 2.4.16.0

RTI Connext DDS Network Binding Library is supported on the following platforms:

OS	CPU	Compiler
Ubuntu Linux 20.04 LTS	x64	gcc 9

4.2. What's New in 4.0.0

There are no changes in DDS Network Binding Library in release 4.0.0.

4.3. Previous Releases

4.3.1. What's New in 3.1.1

4.3.1.1. DDS Network Binding Library now production-ready

This version of the DDS Network Binding Library is no longer experimental (also known previously as a "prototype"). It can be used in a production system.

4.3.1.2. Improved support for DDS deployment configuration

The following DDS Service Interface and Instance Deployment attributes are now supported:

Table 4.1 New Supported Attributes
Subclass	Attributes	Description
DdsServiceInterfaceDeployment	fieldRequestTopicName, fieldReplyTopicName, methodRequestTopicName, and methodReplyTopicName	These attributes define the customizable name suffix of the Topics used in method- and field-based communication.
DdsProvidedServiceInstance	discoveryType and resourceIdentifierType	These attributes define the discovery mechanism (Topic- or Participant-based) and the binding mechanism (Partition, Topic, or InstanceId).
DdsRequiredServiceInstance	discoveryType and blocklistedVersion	These attributes define the discovery mechanism (Topic- or Participant-based) and the blocklisted (that is, ignored during discovery) Service Interface versions.

These new attributes make Adaptive Application deployments using RTI's DDS Network Binding Library more configurable in run-time, allowing changes in DDS Topic naming and discovery without the need to regenerate and recompile application sources.

4.3.2. What's Fixed in 3.1.1

4.3.2.1. Core dump when creating more than one proxy with an associated trigger, event, method, or field

If more than one proxy was created with a registered trigger, event, method, or field, a core dump occurred when calling Enable() in the second proxy.

[RTI Issue ID APIT-417]

4.3.2.2. Potential crash when unregistering a proxy

A race condition that occurred during the execution of a method or a field's getter was identified and resolved on the proxy side. If the method or field was unregistered immediately after a value was received, the DDS Network Binding Library could have crashed because some operations within the method or field were still in progress at the time of unregistration.

[RTI Issue ID APIT-420]

4.3.3. What's New in 3.1.0

Code produced by rtiaragen is now located in CMake's build tree.

4.3.4. What's Fixed in 3.1.0

Multiple service instances of the same service interface caused unexpected behavior under the same process due to mismanagement of shared DDS entities.

[RTI Issue ID APIT-288]

Under certain C++ STL implementations, the key/value file parser crashed upon encountering empty lines.

[RTI Issue ID APIT-290]