Why is TCP_NODELAY settable only on the subscriber side in roscpp, but only the publisher side in rospy? [closed]

asked 2012-10-26 09:50:21 -0500

Patrick Bouffard gravatar image

updated 2014-01-28 17:14:04 -0500

ngrennan gravatar image

I just noticed this while looking into some issues with latency. Just curious why this is the case, and whether there are plans to change it (the roscpp page suggests that setting this on the publisher might be an option in the future).

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2015-09-18 18:43:46.669323

Comments

Is there a reason this cannot be done? I ask because it would be nice to test the TCP_NODELAY option from a Python node, e.g. rostopic.

pumaking gravatar image pumaking  ( 2017-11-07 20:24:47 -0500 )edit

It cannot be done because no one has added that feature to rospy.

ahendrix gravatar image ahendrix  ( 2018-08-24 15:57:07 -0500 )edit
add a comment