Compatibility of Connext Micro with DESTINATION_ORDER QoS

2 posts / 0 new
Last post
Offline
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.

I suppose that this limitation of Micro is a tradeoff to limit the need for computation in the DataReaders when receiving data. However, I think also that sending a sample does not require the same amount of computation. So, could we imagine making possible the use of BY_SOURCE_TIMESTAMP for DataWriter side, and only restrain the DESTINATION_ORDER QoS to BY_RECEPTION_TIMESTAMP for DataReaders?

Best regards.

Jean-François

Offline
Joined: 01/09/2013
Posts: 10

Any comment?

It seems that Connext Micro does not provide any API to modify this QoS. Maybe a change in its source code could be done to modify the value to BY_SOURCE_TIMESTAMP on the DataWriter side?