Some experiments testing roscpp unreliable transports.
When creating a subscriber you can specify hints to make it unreliable (udp) You cannot do anything on the publisher end If the publisher (not roscpp publishers) does not support udp, then tcp connections are made.
One publisher, one unreliable subscriber - udp connection One publisher, one subscriber, one unreliable subscriber - the latter is still udp connection You can observe the unreliable connections being made with:
> watch -n1 ss -u