API

Note: Applies to RTI Connext 4.x and above. RTI Connext uses the concept of exclusive areas (EA) to avoid deadlocks when user listener code calls the RTI Connext APIs. In a nutshell: Each entity has their own EAs. Controlling access into EAs is a way to prevent deadlocking situations. The rule of ...
5351 reads — 0 comments
Note: Relevant RTI Connext versions: NDDS 3.x, RTI Connext 4.x and above You may want to use your own serialize/deserialize functions if there are existing message formats and data structures that you want to keep. In this case, the fastest way to take advantage of RTI Connext’s cross-platform ...
3783 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. What is the trade-off between having one Subscriber with multiple DataReaders , versus multiple Subscribers that each have one DataReader ? Typically, an application will have one Subscriber with multiple DataReaders . If the DataReaders are set up to ...
8408 reads — 0 comments
Note: Applies to NDDS 3.x and RTI Connext 4.x and above. The Java API in NDDS 3.x is based on the JMSRT interface, which is similar to the JMS interface. The Java API in RTI Connext 4.x and above complies with the DDS standard and is much more consistent with its C and C++ interfaces, but is very ...
2089 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0 and 4.1. RTI Data Distribution Service selects well-known static ports based on this formula: 7400 + A * (DomainID + (B * Participant_index)) + (0 | 1 | 2) Where A and B are user-definable, with defaults of 10 and 100, respectively. To run multiple ...
3340 reads — 0 comments
Note: Relevant RTI Connext versions: RTI Connext 4.x and above. There are a few QoS that relate to redundancy. In order to support redundancy, you will want to use the Ownership QoS to specify a strength for each writer and specify DDS_EXCLUSIVE_OWNERSHIP_QOS on both writers and readers. There is ...
5638 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. An example throughput test is provided in NDDSHOME/example/[CPP or Java]/performance/throughput. The most common problem encountered in performance testing is a publisher that is sending too fast for the receiver to process. Symptoms of this include a ...
11104 reads — 0 comments

Pages

Subscribe to RSS - API