Message321874
> write.setsockopt(socket.SOL_SOCKET, socket.SO_SNDBUF, 0)
Instead of that, I also tried:
read.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1)
write.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1)
But I'm able to reproduce the bug with TCP_NODELAY=1 on the write end. (The option should have no impact on the read end, but I added it anyway, just in case, I still reproduce the bug.)
MSDN documentation for TCP_NODELAY:
"Disables the Nagle algorithm for send coalescing.This socket option is included for backward compatibility with Windows Sockets 1.1 "
https://docs.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-setsockopt |
|
Date |
User |
Action |
Args |
2018-07-18 10:16:58 | vstinner | set | recipients:
+ vstinner, pitrou, njs, yselivanov |
2018-07-18 10:16:58 | vstinner | set | messageid: <1531909018.85.0.56676864532.issue34130@psf.upfronthosting.co.za> |
2018-07-18 10:16:58 | vstinner | link | issue34130 messages |
2018-07-18 10:16:58 | vstinner | create | |
|