Deadline is set to 0, it may cause DataReaderImpl::deadline_timer_ timeout immediately about dds-router

[juanlofer-eprosima]

Hi @binbowang1987

Thank you for your comment.

As a design choice, deadline period is set as the least restrictive one in order to match with every found DataReader using this QoS. However, in practice this has no further consequences as this particular QoS only concerns the DDS layer (while DDS-Router operates in the RTPS one). The only catch about this is that endpoints that would not be able to communicate locally (as they would not match) would be able to do so via a DDS-Router instance.

We were able to confirm the expected behavior with this example. Nonetheless, if you were to find any inconsistency in this regard, we would be very thankful to be informed.

Cheers

[binbowang1987]

Hi @juanlofer-eprosima, thank you for your explaination, I get it.

The only catch about this is that endpoints that would not be able to communicate locally (as they would not match) would be able to do so via a DDS-Router instance.

I think this is not a problem, router's main ability is to transfer dds topic data. As design, is it not responsible for fully qos compatibility.