Release/connector/1.1.0 (#57)

* Mention node.js support in getting_started.rst * Feature/con 173 node12 test (#14) * CON-173: Creating temporary remote branch for testing * CON-173: Update dependencies to RTI-managed repos * CON-173: Revert changes to connector * CON-177: Added support for sample/view/instance state (#15) * CON-177: Added support for sample/view/instance state * CON-177: PR feedback - Indicate possible values of the new fields in the docs - Use the naming conventions for strings in unit tests * CON-173: Fixed unit tests which were failing Some items had been added to a JSON object but not in the other JSON object we were checking. This ocurred when adding support for CON-177 * CON-173: Update docs so that we don't mention node 8 (#17) * CON-173: Update docs so that we don't mention node 8 * CON-173: PR feedback #time 5m Remove paragraph mentioning Node 12 incompatibility. Co-authored-by: Sam Raeburn <sam@rti.com> * Feature/con 188 (#18) * CON-188: Added docs + tests * CON-188: Revert changes to package.json * CON-188: Change of functionality Previously, any non-key fields would be returned as null when obtain via DD_GET operations. This is no longer the case. * CON-188: Remove debug * CON-188: PR feedback - doc related * CON-188: PR Feedback - Do not access non-key fields in the unit tests - Fix docs Co-authored-by: Sam Raeburn <sam@rti.com> * CON-209: Js doc update * Update README.md (#19) Fixing the link to OpenLayers * Feature/con 163 test (#23) * CON-163: Added test for CON-163 * CON-209: Added unit test for CON-209 Co-authored-by: Sam Raeburn <sam@rti.com> * CON-212: Added CONTRIBUTING.md file (#21) Co-authored-by: Sam Raeburn <sam@rti.com> * CON-214: Test for creating Connector with participant_qos (#24) Co-authored-by: Sam Raeburn <sam@rti.com> * CORE-10744: Updating docs for new system resource defaults (#26) Co-authored-by: Sam Raeburn <sam@rti.com> * CON-211: updating links to other manuals for connector-js * CON-211: in -js, updated GSG title and fixed an error in a GSG cross-reference * CON-188: Updated instance support section of features.rst (#29) Co-authored-by: Sam Raeburn <sam@rti.com> * Feature/con 173 napi (#27) * CON-173: Use 3rd-party managed *-napi packages * Update documentation * Fixed docs * Fix list * CON-173: Update packages used in code * CON_173: Correct struct package Co-authored-by: Sam Raeburn <sam@rti.com> * GREEN-1938: Use the ffi-napi modules in tests (#30) Some of the unit tests were requiring the ffi modules to test the ability to extend the API. Since we updated package.json to use the ffi-napi module, the ffi module is no longer present and these tests were failing. Co-authored-by: Sam Raeburn <sam@rti.com> * Updated documentation to explain that we do not support Node 12.19.0. (#31) Co-authored-by: Sam Raeburn <sam@rti.com> * Feature/con 217 (#33) * Fixed sockets.io example * feature/CON218: Added graph example * Updated example README Co-authored-by: Sam Raeburn <sam@rti.com> * PLATFORMS-1925. Updated supported platforms to match Hercules PAM. * Introduce EOL normalization (#32) * CON-174: Handle armv8 architectures (#37) Co-authored-by: Sam Raeburn <sam@rti.com> * CON-221: Added docs for the dynamic loading of libraries (#39) Co-authored-by: Sam Raeburn <sam@rti.com> * CORE-11069: Customer facing XML has been updated (#38) * CORE-11069: Customer facing XML has been updated * CORE-11069: Update XML used in tests Co-authored-by: Sam Raeburn <sam@rti.com> * Feature/con 220 (#34) * Updated package.json to not use asterisk for dependency versions * Committed the generated package-lock.json * Updated README containing additional dependencies to state specific version Co-authored-by: Sam Raeburn <sam@rti.com> * CON-211: removed a statement per reviewer feedback after resolving conflicts * CON-215: Added release notes (#25) * CON-215: Added release notes * CON-215: Added notes for CON-188 * CON-215: Added more issues to notes * CON-215: Added issue num * Update docs/release_notes.rst * Update docs/release_notes.rst * Apply suggestions from code review * Update docs/release_notes.rst * Update docs/release_notes.rst * CON-215: making same changes to Javascript docs as I made to Python ones, mainly for release notes * CON-215: PR feedback * PR feedback - Fix typo Co-authored-by: Sam Raeburn <sam@rti.com> Co-authored-by: rkorte <rkorte@rti.com> * restore 'LICENSE.pdf' to git from lfs * Removed the gitattributes file since it now has no use * GREEN-2058: Added tests for new functionality in DD parser (#41) Co-authored-by: Sam Raeburn <sam@rti.com> * Updated native libs * Feature/dir renames (#43) * Updating directory names when searching for native libs * - Update commit to submodule - Remove support for 32-bit windows + Linux * Update commit of native libs * Explicitly load library dependencies on Windows * Fix loading of extra libs Co-authored-by: Sam Raeburn <sam@rti.com> * Updated platforms * Removed symbol from ARMv7 platform * Updated submodule to feature/update-libs-for-internal-rel (#45) Co-authored-by: Sam Raeburn <sam@rti.com> * Feature/release notes fix (#46) * - Fixed formatting of release notes - Updated version in docs * - Added static method to Connector class providing current version. * fix typo * - Set version to 1.1.0 in docs - Remove version() functions - needs further thought on implementation - Updated docs to use RTI blue colour Co-authored-by: Sam Raeburn <sam@rti.com> * Update README in web socket example (#48) * Update README in web socket example * Fix formatting Co-authored-by: Sam Raeburn <sam@rti.com> * Added Ubuntu 16.04 to release notes (x64, Armv8) (#47) * Added Ubuntu 16.04 to release notes (x64, Armv8) * Added ARMv8 support to whats new 1.1.0 * fix typo Co-authored-by: Sam Raeburn <sam@rti.com> * Update minimum supported version of node v10 in docs (#49) Co-authored-by: Sam Raeburn <sam@rti.com> * CON-211: testing all links to core docs, fixing few that were broken - js * CON-215: added two new js release notes * CON-194: js changes: updated copyrights, added logging to match python * CON-194: Added additional setence to Managing Data Instances section. * HERCULES-186: updates to licenses doc for javascript * Add support for loading 32-bit libs if present (#54) * Add support for loading 32-bit libs if present * Update rticonnextdds-connector.js Co-authored-by: Alex Campos <alejandro@rti.com> Co-authored-by: Sam Raeburn <sam@rti.com> Co-authored-by: Alex Campos <alejandro@rti.com> * HERCULES-186: modified lua and json-parser lines for Connector js * Document dependency on Connext version from dynamic libs (#56) * Document dependency on Connext version from dynamic libs * PR feedback Clarified wording & added link * PR feedback Co-authored-by: Sam Raeburn <sam@rti.com> * Update native libraries to version 6.1.0 * Update README for version 1.1.0 * Update package.json for version 1.1.0 Co-authored-by: Alex Campos <alejandro@rti.com> Co-authored-by: Sam Raeburn <sam@rti.com> Co-authored-by: Alex Campos <alex@rti.com> Co-authored-by: Rabbi Shuki Gur <rabbishuki@users.noreply.github.com> Co-authored-by: rkorte <rkorte@rti.com> Co-authored-by: Adelle Olson <adelle@rti.com> Co-authored-by: rkorte <36715349+rkorte@users.noreply.github.com>
rticommunity · May 3, 2021 · 2247ef8 · 2247ef8
1 parent 7bb63c4
commit 2247ef8
Show file tree

Hide file tree

Showing 36 changed files with 1,603 additions and 221 deletions.
diff --git a/.gitattributes b/.gitattributes
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,4 @@
+# Contributing to RTI Connector for JavaScript
+
+### Contributor License Agreement (CLA)
+In order to accept your pull request, we need you to sign a Contributor License Agreement (CLA). Complete your CLA here: http://community.rti.com/cla. You only need to do this once, we cross-check your Github username with the list of contributors who have signed the CLA.
diff --git a/README.md b/README.md
@@ -26,11 +26,12 @@ The `examples/nodejs` directory provides several examples:
 ## Dependencies
 
 RTI Connector for JavaScript has the following dependencies, which are also listed in `package.json`:
-* [ref](https://www.npmjs.com/package/ref): turns Buffer instances into "pointers"
-* [ffi](https://www.npmjs.com/package/ffi): used for loading and calling dynamic libraries using pure JavaScript
+* [ref-napi](https://www.npmjs.com/package/ref-napi): turns Buffer instances into "pointers"
+* [ref-struct-napi](https://www.npmjs.com/package/ref-struct-napi): create ABI-compilant "Struct" instances on top of Buffers
+* [ffi-napi](https://www.npmjs.com/package/ffi-napi): used for loading and calling dynamic libraries using pure JavaScript
 * [events](https://www.npmjs.com/package/events): used for the 'EventEmitter' (legacy implementation of RTI Connector)
 
-Additionally to run the `web_socket` example, [socket.io](https://github.com/Automattic/socket.io) and [OpenLayers](hhttps://openlayers.org] are required.
+Additionally to run the `web_socket` example, [socket.io](https://github.com/Automattic/socket.io) and [OpenLayers](https://openlayers.org) are required.
 
 Additional dependencies are required to run the unit tests and some of the examples. Please see the README files in the appropriate directory.
 

diff --git a/README.rst b/README.rst
@@ -2,7 +2,7 @@ RTI Connector for JavaScript
 ============================
 
 RTI® Connext® DDS is a connectivity software framework for integrating
-data sources of all types. At its core is the world’s leading ultra-high
+data sources of all types. At its core is the world's leading ultra-high
 performance, distributed networking databus.
 
 *RTI Connector* provides a quick and easy way to write applications that
@@ -34,15 +34,18 @@ Dependencies
 
 RTI Connector for JavaScript has the following dependencies, which are
 also listed in ``package.json``: \*
-`ref <https://www.npmjs.com/package/ref>`__: turns Buffer instances into
-“pointers” \* `ffi <https://www.npmjs.com/package/ffi>`__: used for
-loading and calling dynamic libraries using pure JavaScript \*
+`ref-napi <https://www.npmjs.com/package/ref-napi>`__: turns Buffer
+instances into "pointers" \*
+`ref-struct-napi <https://www.npmjs.com/package/ref-struct-napi>`__:
+create ABI-compilant "Struct" instances on top of Buffers \*
+`ffi-napi <https://www.npmjs.com/package/ffi-napi>`__: used for loading
+and calling dynamic libraries using pure JavaScript \*
 `events <https://www.npmjs.com/package/events>`__: used for the
-‘EventEmitter’ (legacy implementation of RTI Connector)
+'EventEmitter' (legacy implementation of RTI Connector)
 
 Additionally to run the ``web_socket`` example,
 `socket.io <https://github.com/Automattic/socket.io>`__ and
-[OpenLayers](hhttps://openlayers.org] are required.
+`OpenLayers <https://openlayers.org>`__ are required.
 
 Additional dependencies are required to run the unit tests and some of
 the examples. Please see the README files in the appropriate directory.

diff --git a/docs/advanced.rst b/docs/advanced.rst
@@ -1,4 +1,4 @@
-Advanced topics
+Advanced Topics
 ===============
 
 .. toctree::

diff --git a/docs/conf.py b/docs/conf.py
@@ -17,12 +17,12 @@
 # -- Project information -----------------------------------------------------
 
 project = 'RTI Connector for JavaScript'
-copyright = '2019, Real-Time Innovations, Inc.'
+copyright = '2021, Real-Time Innovations, Inc.'
 author = 'Real-Time Innovations, Inc.'
 
 # The full version, including alpha/beta/rc tags
-release = '1.0.0'
-version = '1.0.0'
+release = '1.1.0'
+version = '1.1.0'
 
 master_doc = 'index'
 primary_domain = 'js'

diff --git a/docs/configuration.rst b/docs/configuration.rst
@@ -1,7 +1,7 @@
 
 .. py:currentmodule:: rticonnextdds_connector
 
-Defining a DDS system in XML
+Defining a DDS System in XML
 ==============================
 
 *Connector* loads the definition of a DDS system from an XML configuration file
@@ -12,7 +12,7 @@ and *DataWriters*, data types and quality of service.
     :align: center
 
 *Connector* uses the XML schema defined by RTI's
-`XML-Based Application Creation feature <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/xml_application_creation/html_files/RTI_ConnextDDS_CoreLibraries_XML_AppCreation_GettingStarted/index.htm>`__.
+`XML-Based Application Creation feature <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/xml_application_creation/index.htm>`__.
 
 .. hint::
     The *Connext DDS* C, C++, Java and .NET APIs can also load the same XML files
@@ -75,11 +75,11 @@ and ``shapesize``:
 Types are associated with *Topics*, as explained in the next section, :ref:`Domain Library`.
 
 .. hint::
-    You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/code_generator/html_files/RTI_CodeGenerator_UsersManual/index.htm#code_generator/UsersManual/UsersManual_Title.htm>`__.
+    You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/code_generator/users_manual/index.htm>`__.
     For example: ``rtiddsgen -convertToXml MyTypes.idl``
 
 For more information about defining types, see
-`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/Creating_User_Data_Types_with_Extensible.htm>`__
+`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Creating_User_Data_Types_with_Extensible.htm>`__
 in the *Connext DDS Core Libraries User's Manual*.
 
 For more information about accessing the data samples, see :ref:`Accessing the data`.
@@ -89,10 +89,10 @@ Domain library
 
 A domain library is a collection of domains. A domain specifies:
 
-  * A `domain id <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/ChoosingDomainID.htm>`__.
+  * A `domain id <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/ChoosingDomainID.htm>`__.
   * A set of registered types (from a subset of the types in ``<types>``).
     A registered type can have a local name.
-  * A set of `topics <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/WorkingWithTopics.htm>`__,
+  * A set of `topics <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/WorkingWithTopics.htm>`__,
     which are used by *DataReaders* and *DataWriters*.
 
 .. code-block:: xml
@@ -106,7 +106,7 @@ A domain library is a collection of domains. A domain specifies:
     </domain_library>
 
 For more information about the format of a domain library, see
-`XML-Based Application Creation: Domain Library <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/xml_application_creation/html_files/RTI_ConnextDDS_CoreLibraries_XML_AppCreation_GettingStarted/index.htm#XMLBasedAppCreation/UnderstandingPrototyper/DomainLibrary.htm#5.5.1_Domain_Library%3FTocPath%3D5.%2520Understanding%2520XML-Based%2520Application%>`__.
+`XML-Based Application Creation: Domain Library <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/DomainLibrary.htm>`__.
 
 Participant library
 ~~~~~~~~~~~~~~~~~~~
@@ -139,12 +139,12 @@ as described in :ref:`Reading data (Input)`.
     </domain_participant_library>
 
 For more information about the format of a participant library, see
-`XML-Based Application Creation: Participant Library <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/xml_application_creation/html_files/RTI_ConnextDDS_CoreLibraries_XML_AppCreation_GettingStarted/index.htm>`__.
+`XML-Based Application Creation: Participant Library <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/ParticipantLibrary.htm>`__.
 
 Quality of service
 ~~~~~~~~~~~~~~~~~~
 
-All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/QosPolicies.htm>`__.
+All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/QosPolicies.htm>`__.
 There are several ways to configure it.
 
 You can define a QoS profile and make it the default. The following example
@@ -178,7 +178,7 @@ You can define the QoS for each individual entity:
 .. code-block:: xml
 
     <domain_participant name="MyPubParticipant" domain_ref="MyDomainLibrary::MyDomain">
-        <participant_qos> <!-- ... --> </participant_qos>
+        <domain_participant_qos> <!-- ... --> </domain_participant_qos>
         <publisher name="MyPublisher">
             <publisher_qos> <!-- ... --> </publisher_qos>
             <data_writer name="MySquareWriter" topic_ref="Square">
@@ -200,9 +200,9 @@ entity:
 .. code-block:: xml
 
     <domain_participant name="MyPubParticipant" domain_ref="MyDomainLibrary::MyDomain">
-        <participant_qos base_name="MyQosLibrary::MyQosProfile">
+        <domain_participant_qos base_name="MyQosLibrary::MyQosProfile">
             <!-- override or configure additional Qos policies -->
-        </participant_qos>
+        </domain_participant_qos>
         <publisher name="MyPublisher">
             <publisher_qos base_name="MyQosLibrary::MyQosProfile">
                 <!-- override or configure additional Qos policies -->
@@ -230,4 +230,23 @@ profile is equivalent to *MyQosProfile* above:
     </qos_library>
 
 You can read more in the *RTI Connext DDS Core Libraries User's Manual*, 
-`Configuring QoS with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/XMLConfiguration.htm>`__.
+`Configuring QoS with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/XMLConfiguration.htm>`__.
+
+Logging
+^^^^^^^
+
+Logging can be configured as explained in `Configuring Logging via XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Configuring_Logging_via_XML1.htm>`__.
+
+For example, to increase the logging verbosity from the default (ERROR) to
+WARNING, define a ``qos_profile`` with the attribute
+``is_default_participant_factory_profile="true"``:
+
+.. code-block:: xml
+
+    <qos_profile name="Logging" is_default_participant_factory_profile="true">
+        <participant_factory_qos>
+            <logging>
+                <verbosity>WARNING</verbosity>
+            </logging>
+        </participant_factory_qos>
+    </qos_profile>
diff --git a/docs/connector.rst b/docs/connector.rst
@@ -22,7 +22,7 @@ To create a new :class:`Connector`, pass an XML file and a configuration name to
    const connector = new rti.Connector('MyParticipantLibrary::MyParticipant', 'ShapeExample.xml')
 
 The XML file defines your types, QoS profiles, and DDS Entities. *Connector*
-uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/xml_application_creation/html_files/RTI_ConnextDDS_CoreLibraries_XML_AppCreation_GettingStarted/index.htm#XMLBasedAppCreation/UnderstandingPrototyper/XMLTagsConfigEntities.htm%3FTocPath%3D5.%2520Understanding%2520XML-Based%2520Application%2520Creation%7C5.5%2520XML%2520Tags%2520for%2520Configuring%2520Entities%7C_____0>`__.
+uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
 
 The previous code loads the ``<domain_participant>`` named *MyParticipant* in
 the ``<domain_participant_library>`` named *MyParticipantLibrary*, which is defined in the
@@ -42,7 +42,7 @@ When you create a :class:`Connector`, the DDS *DomainParticipant* that you selec
 and all of its contained entities (*Topics*, *Subscribers*, *DataReaders*,
 *Publishers*, *DataWriters*) are created.
 
-For more information about the DDS entities, see `Part 2 - Core Concepts <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/PartCoreConcepts.htm#partcoreconcepts_4109331811_915546%3FTocPath%3DPart%25202%253A%2520Core%2520Concepts%7C_____0>`__
+For more information about the DDS entities, see `Core Concepts <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/PartCoreConcepts.htm>`__
 in the *RTI Connext DDS Core Libraries User's Manual*.
 
 .. note::
@@ -90,8 +90,8 @@ returns the :class:`Input` that allows reading data.
 
 For more information see:
 
-    * :ref:`Writing data (Output)`
-    * :ref:`Reading data (Input)`
+    * :ref:`Writing Data (Output)`
+    * :ref:`Reading Data (Input)`
 
 Class reference: Connector
 ~~~~~~~~~~~~~~~~~~~~~~~~~~

diff --git a/docs/copyright_license.rst b/docs/copyright_license.rst
@@ -6,10 +6,10 @@
 Copyrights and License
 **********************
 
-© 2019 Real-Time Innovations, Inc. |br|
+© 2021 Real-Time Innovations, Inc. |br|
 All rights reserved.  |br|
 Printed in U.S.A. First printing.  |br|
-November 2019. |br|
+April 2021. |br|
 
 .. rubric:: License
 
@@ -42,7 +42,10 @@ This is an independent publication and is neither affiliated with, nor
 authorized, sponsored, or approved by, Microsoft Corporation.
 
 The security features of this product include software developed by the
-OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
+OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). 
+his product includes cryptographic software written by Eric Young 
+(eay@cryptsoft.com). This product includes software written by Tim Hudson 
+(tjh@cryptsoft.com).
 
 Technical Support |br|
 Real-Time Innovations, Inc. |br|
@@ -52,4 +55,64 @@ Phone: (408) 990-7444 |br|
 Email: support@rti.com |br|
 Website: https://support.rti.com/ |br|
 
-© 2019 RTI
+© 2021 RTI
+
+.. rubric:: External Third-Party Software Used in Connector
+
+**Lua**
+  * The source code of this software is used to build the native libraries
+    provided by *RTI Connector*.
+
+  * License (https://www.lua.org/license.html):
+    Copyright © 1994–2021 Lua.org, PUC-Rio.
+
+    Permission is hereby granted, free of charge, to any person obtaining a 
+    copy of this software and associated documentation files (the "Software"), 
+    to deal in the Software without restriction, including without limitation 
+    the rights to use, copy, modify, merge, publish, distribute, sublicense, 
+    and/or sell copies of the Software, and to permit persons to whom the 
+    Software is furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included 
+    in all copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
+    OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL 
+    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+    THE SOFTWARE.
+
+**json-parser**
+  * The source code of this software (from https://github.com/udp/json-parser) 
+    is used to build the native libraries provided by *RTI Connector*.
+
+  * License:
+
+    Copyright (C) 2012, 2013, 2014 James McLaughlin et al.  All rights reserved.
+    https://github.com/udp/json-parser
+
+    Redistribution and use in source and binary forms, with or without
+    modification, are permitted provided that the following conditions
+    are met:
+
+    1. Redistributions of source code must retain the above copyright
+       notice, this list of conditions and the following disclaimer.
+
+    2. Redistributions in binary form must reproduce the above copyright
+       notice, this list of conditions and the following disclaimer in the
+       documentation and/or other materials provided with the distribution.
+
+    THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+    ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+    ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+    FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+    DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+    OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+    SUCH DAMAGE.
+