Rticonnextdds-connector

RTI Connector 1.2.4 is built on RTI Connext DDS 6.1.2.21, which fixes several bugs in the Core Libraries. For details, contact [supportrti.com](mailto:supportrti.com). See the release notes for RTI Connector for Python 1.2.4 [here](https://community.rti.com/static/documentation/connector/1.2.4/api/python/release_notes.html).

RTI Connector 1.2.3 is built on RTI Connext DDS 6.1.2.17, which fixes several bugs in the Core Libraries. For details, contact supportrti.com. See the release notes for RTI Connector for Python 1.2.3 [here](https://community.rti.com/static/documentation/connector/1.2.3/api/python/release_notes.html).

RTI Connector 1.2.2 is built on RTI Connext DDS 6.1.2. See the release notes for RTI Connector for Python 1.2.2 [here](https://community.rti.com/static/documentation/connector/1.2.2/api/python/release_notes.html).

RTI Connector 1.2.0 is built on RTI Connext DDS 6.1.1. See the release notes for RTI Connector for Python 1.2.0 [here](https://community.rti.com/static/documentation/connector/1.2.0/api/python/release_notes.html).

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 supportrti.com.

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:

c = rti.Connector("my_profiles.xml;my_types.xml;my_participants.xml", configName)

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.
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.
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.