Message321879
➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | vstinner |
|---|---|
| Recipients | njs, pitrou, vstinner, yselivanov |
| Date | 2018-07-18.10:48:02 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1531910882.54.0.56676864532.issue34130@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I found two different articles on microsoft.com which confirms that SO_SNDBUF=0 is valid and is intended to completely disable kernel buffering: * https://support.microsoft.com/en-gb/help/181611/socket-overlapped-i-o-versus-blocking-nonblocking-mode * https://blogs.msdn.microsoft.com/larryosterman/2004/08/06/the-consequences-of-ignoring-nagling-and-delayed-acks/ "If SO_SNDBUF=0, each send() or WriteFile() must wait for an acknowledgement from the other side before returning. (That is the only way for the protocol to implement retransmissions)" |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-18 10:48:02 | vstinner | set | recipients: + vstinner, pitrou, njs, yselivanov |
| 2018-07-18 10:48:02 | vstinner | set | messageid: <1531910882.54.0.56676864532.issue34130@psf.upfronthosting.co.za> |
| 2018-07-18 10:48:02 | vstinner | link | issue34130 messages |
| 2018-07-18 10:48:02 | vstinner | create | |