DESTINATION_ORDER

3 posts / 0 new
Log in or register to post comments
Last post
Wed, 10/11/2017 - 11:00
#1
gustavo@rti.com
gustavo@rti.com's picture
Offline
Last seen: 2 years 8 months ago
Joined: 03/06/2017
Posts: 1
Understanding by_source and source_timestamp_tolerance at the DataWriter side

Hi,

I have a question regarding Destination Order QoS, by_source_timestamp and source_timestamp_tolerance at the DW side.

At the DR the behavior is clear for me, I have tests and validated all behaviors. My question is about to the DW side, and the source_timestamp_tolerance at the DW.

According to the docs, if I have a DataWriter with kind DDS_BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS:

Organization:
Keywords:
Top
3 posts / 0 new
Log in or register to post comments
Last post
Tue, 03/28/2017 - 12:49
#1
jftilman
Offline
Last seen: 12 months 2 days ago
Joined: 01/09/2013
Posts: 10
Compatibility of Connext Micro with DESTINATION_ORDER QoS

The documentation explains that Connext Micro supports only BY_RECEPTION_TIMESTAMP for the DESTINATION_ORDER QoS. Thus, a Micro application will be able to receive data from a full-DDS application with BY_SOURCE_TIMESTAMP, but not send data to this application.

Keywords:
Top
Subscribe to RSS - DESTINATION_ORDER