You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rfc2217 protocol handler sets TCP_NODELAY (from inspection of the code it looks like it does anyway). The socket protocol handler doesn’t (at least, I don’t see any reference to it in that protocol handler, and also I getsockopted the socket and it wasn’t set). That seems inconsistent, and as far as I can tell it’s also not documented. It might be nice if the application could control it. It might be nice if it were consistent between protocols. If nothing else, it would be great if the situation were documented so the application can make sure not to fall into the Nagle+delayed ACK trap.
The
rfc2217
protocol handler setsTCP_NODELAY
(from inspection of the code it looks like it does anyway). Thesocket
protocol handler doesn’t (at least, I don’t see any reference to it in that protocol handler, and also Igetsockopt
ed the socket and it wasn’t set). That seems inconsistent, and as far as I can tell it’s also not documented. It might be nice if the application could control it. It might be nice if it were consistent between protocols. If nothing else, it would be great if the situation were documented so the application can make sure not to fall into the Nagle+delayed ACK trap.This issue has been cloned from: pyserial#768
The text was updated successfully, but these errors were encountered: