I have some issues with rtiddsrotuer, where some QoS settings i give it doesnt seem to bite.
In the QoS I have given datareader_qos, datawriter_qos and topic_qos destination order: "BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS". But when i look in Adminconsole i see that the router requests _RECEPTION_. And the main issue is when the unpacking router then supplies _RECEPTION_ to my applications (readers) expecting _SOURCE_ (which is incompatilbe).
Hello,
Currently, I am running RTI Perftest to learn more about the effect of QoS policies on throughput and latency. I am interested to change the PRESENTATION QoS policy in the perftest_qos_profiles.xml file.
<publisher_qos>
<presentation>
<access_scope>TOPIC_PRESENTATION_QOS</access_scope>
<ordered_access>true</ordered_access>
</presentation>
</publisher_qos>
Hi all,
I have a Routing Service set up to relay data received on domain 1 (asymmetric TCP) to domain 0 (shmem) and a remote application that pumps data into domain 1 so that a client application of mine can consume it in domain 0.
However, when I start up the system, the RTI admin console presents me with the following problem:
Hi. I would like to know how to use PRESENTATION QOS with listener properly.
I know that there are 3 ways to receive data.
1. explicitly call read() or take()
2. listener call back ( on_data_available() )
3. waitset
I use 2nd way to receive data.
