Bug #1518

RSB_TRANSPORT_SOCKET_NODELAY documentation seems erroneous

Added by Anonymous almost 11 years ago. Updated almost 11 years ago.

Status:ResolvedStart date:05/28/2013
Priority:NormalDue date:
Assignee:J. Moringen% Done:

100%

Category:Documentation
Target version:rsb-0.9

Description

In the RSB manual, tcp_nodelay for the socket transport is documented to be set through the environment variable RSB_TRANSPORT_SOCKET_NODELAY, where in fact it is RSB_TRANSPORT_SOCKET_TCPNODELAY (at least for c++).

This might be pointing to an inconsistency between the different language implementations (it seems to be just nodelay instead of tcpnodelay in CL, although I'm not an expert in reading CL code).


Related issues

Related to Robotics Service Bus - Bug #1517: TCPNODELAY is off by default in C++ Resolved 05/28/2013
Related to Robotics Service Bus - Bug #1519: Option for controlling TCP_NODELAY has wrong name in CL i... Resolved 05/28/2013

Associated revisions

Revision c0f78250
Added by J. Moringen almost 11 years ago

Fixed RSB_TRANSPORT_SOCKET_{NODELAY -> TCPNODELAY} in common.rst

fixes #1518

  • common.rst: fixed name of environment variable
    RSB_TRANSPORT_SOCKET_{NODELAY -> TCPNODELAY} to match description in
    specification-socket.rst and implementations

History

#1 Updated by Anonymous almost 11 years ago

#2 Updated by J. Moringen almost 11 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

Applied in changeset rsb-manual|commit:c0f78250c62c74c96a7271043b0b617760af65b6.

Also available in: Atom PDF