8. Release Notes¶
8.1. Supported Platforms¶
RTI Connector for JavaScript has been tested with Node.js versions 10.22.0, 11.15.0 and 12.13.0.
Connector uses a native C library that works on most Windows®, Linux® and macOS® platforms. It has been tested on the following systems:
- Linux
CentOS™ 6.0, 6.2-6.4, 7.0 (x64)
Red Hat® Enterprise Linux 6.0-6.5, 6.7, 6.8, 7, 7.3, 7.5, 7.6, 8 (x64)
SUSE® Linux Enterprise Server 12 SP2 (x64)
Ubuntu® 14.04, 16.04, 18.04, 20.04 LTS (x64)
Ubuntu 16.04, 18.04 LTS (64-bit Arm® v8)
Ubuntu 18.04 LTS (32-bit Arm v7)
Wind River® Linux 8 (Arm v7) (Custom-supported platform)
- macOS
macOS 10.13-10.15 (x64)
- Windows
Windows 8 (x64)
Windows 10 (x64)
Windows Server 2012 R2 (x64)
Windows Server 2016 (x64)
Connector is supported in other languages in addition to JavaScript, see the main Connector repository.
8.2. Version 1.1.1¶
RTI Connector 1.1.1 is built on RTI Connext DDS 6.1.0.3, which fixes several bugs in the Core Libraries. For details, contact support@rti.com.
8.3. Version 1.1.0¶
RTI Connector 1.1.0 is built on RTI Connext DDS 6.1.0.
8.3.1. What’s New in 1.1.0¶
8.3.1.1. Support added for ARMv8 architectures¶
Connector for JavaScript now runs on ARMv8 architectures. Native libraries built for ARMv8 Ubuntu 16.04 are now shipped alongside Connector. These libraries have been tested on ARMv8 Ubuntu 16.04 and ARMv8 Ubuntu 18.04.
8.3.1.2. Support added for Node.js version 12¶
Previously, Node.js version 12 was not supported in Connector for JavaScript. Support has been added for Node.js version 12 (the current LTS), and support has been dropped for Node.js version 8 (which has been deprecated). Note that Node.js version 12.19.0 is incompatible with Connector for JavaScript due to a regression in that release of Node.js. Versions 12.18.x and 12.20.x are compatible with Connector for JavaScript.
8.3.1.3. Sample state, instance state and view state can now be obtained in Connector¶
The SampleInfo() class in Connector has been extended to provide access to the
sample state, view state, and instance state fields. These new fields work the
same as the existing fields in the structure (in Connector for Python they are
the keys to the dictionary, in Connector for JavaScript they are the keys to the
JSON Object). See Accessing sample meta-data for more information on this
new feature.
8.3.1.4. Support for accessing the key values of disposed instances¶
Support for disposing instances was added in Connector 1.0.0. However, it was not possible to access the key values of the disposed instance. This functionality is now available in the Python and JavaScript bindings. When a disposed sample is received, the key values can be accessed. The syntax for accessing these key values is the same as when the sample contains valid data (i.e., using type-specific getters, or obtaining the entire sample as an object). When the instance state is NOT_ALIVE_DISPOSED, only the key values in the sample should be accessed. See Accessing key values of disposed samples for more information on this new feature.
8.3.1.5. Connector for Javascript dependencies now locked to specific versions¶
package-lock.json has been committed, fixing the versions of Connector for
Javascript’s dependencies.
8.3.1.6. Support for Security, Monitoring and other Connext DDS add-on libraries¶
It is now possible to load additional Connext DDS libraries at runtime. This means that Connext DDS features such as Monitoring and Security Plugins are now supported. Refer to Loading Connext DDS Add-On Libraries for more information.
8.3.2. What’s Fixed in 1.1.0¶
8.3.2.1. Creating two instances of Connector resulted in a license error¶
Under some circumstances, it was not possible to create two Connector objects. The creation of the second Connector object failed due to a license error. This issue affected all of the Connector APIs (Python, JavaScript). This issue has been fixed.
[RTI Issue ID CON-163]
8.3.2.2. Some larger integer values may have been corrupted by Connector’s internal JSON parser¶
The internal JSON parser used in Connector failed to identify integer numbers from double-precision floating-point numbers for certain values. For example, if a number could not be represented as a 64-bit integer, the parser may have incorrectly identified it as an integer, causing the value to become corrupted. This problem has been resolved.
[RTI Issue ID CON-170]
8.3.2.3. Support for loading multiple configuration files¶
A Connector object now supports loading multiple files. This allows separating the definition of types, QoS profiles, and DomainParticipants into different files:
const connector = new rti.Connector("my_profiles.xml;my_types.xml;my_participants.xml", configName)
[RTI Issue ID CON-209]
8.3.2.4. Creating a Connector instance with a participant_qos tag in the XML may have resulted in a license error¶
In some cases, if the XML configuration file of Connector contained a <participant_qos> tag within the definition of the DomainParticipant, the creation of the Connector would fail with a “license not found” error. This problem has been resolved.
[RTI Issue ID CON-214]
8.3.2.5. Websocket example may have failed to run¶
The websocket example (available only in Connector for Javascript) may have failed to run due to one of its dependencies, socket.io, removing a public API. This problem has been resolved.
[RTI Issue ID CON-217]
8.4. Version 1.0.0¶
1.0.0 is the first official release of RTI Connector for JavaScript as well as RTI Connector for Python.
If you had access to previous experimental releases, this release makes the product more robust, modifies many APIs and adds new functionality. However the old APIs have been preserved for backward compatibility as much as possible.
RTI Connector 1.0.0 is built on RTI Connext DDS 6.0.1.