Message311414
So we either need to explicitly exclude this symbol on Windows (at least until we drop support for pre-Windows 10 versions) or silently ignore setsockopt errors for future good arguments. I'm inclined to do the former - other opinions?
--------------
I'm not a socket expert, I have a question about the former one.
Imagine someone changed those values in his/her code, for example:
socket.TCP_KEEPCNT = 20
His/her code works fine on new version Windows. Will this line break things again on old version Windows? |
|
Date |
User |
Action |
Args |
2018-02-01 10:04:22 | malin | set | recipients:
+ malin, paul.moore, tim.golden, ned.deily, zach.ware, steve.dower, thatiparthy, tjguk, skn78 |
2018-02-01 10:04:22 | malin | set | messageid: <1517479462.39.0.467229070634.issue32394@psf.upfronthosting.co.za> |
2018-02-01 10:04:22 | malin | link | issue32394 messages |
2018-02-01 10:04:22 | malin | create | |
|