14.1. Supported Platforms
See the Routing Service column in the Table of Supported Platforms for Compiler-Dependent Products, in the RTI Connext Core Libraries Release Notes.
Routing Service can also be deployed as a C library linked into your application.
For backward compatibility information between the current and previous versions of Routing Service, please see the Migration Guide on the RTI Community portal.
Routing Service can be used to forward and transform data between applications built with Connext, as well as RTI Data Distribution Service 4.5[b-e], 4.4d, 4.3e, and 4.2e except as noted below.
Routing Service is not compatible with applications built with RTI Data Distribution Service 4.5e and earlier releases when communicating over shared memory. For more information, please see the Transport Compatibility section in the Migration Guide on the RTI Community portal.
Starting in Connext 5.1.0, the default
message_size_maxfor the UDPv4, UDPv6, TCP, and shared-memory transports changed to provide better out-of-the-box performance. Routing Service also uses the new value for
message_size_max. Consequently, Routing Service is not out-of-the-box compatible with applications running older versions of Connext. Please see the RTI Connext DDS Core Libraries Release Notes for instructions on how to resolve this compatibility issue with older Connext applications.
The types of the remote administration and monitoring topics in 5.1.0 are not compatible with 5.0.0. Therefore:
The 5.0.0 RTI Routing Service shell, RTI Admin Console 5.0.0, and RTI Connext DDS 5.0.0 user applications performing monitoring/administration are not compatible with RTI Routing Service 5.1.0.
The 5.1.0 RTI Routing Service shell, RTI Admin Console 5.1.0, and RTI Connext DDS 5.1.0 user applications performing monitoring/administration are not compatible with RTI Routing Service 5.0.0.