You are right! I remember(ed) this thread you linked to but I thought it was a different issue.
In fact it's the same issue. I assume that if you didn't answer that thread at the end it's because you agree with Saturn that it's correct behavior (although he wasn't so sure himself at the end
)?
For reference, why this has been bugging me is that, the server use both TCP and UDP, it runs a timer and send udp packet to clients each 45 ms. When clients issue a 'quit', they do so with tcp, but they immediately close the UDP socket, meaning the server will still try to send them packet, until it gets the tcp message.
Of course this is now crystal clear to me, but it wasn't so clear 5 years ago
It's a simple fix for my script, I just need to let the udp socket running on client and ignore further packets until the server get the quit on the tcp socket and remove the client from the list of ip/port to send packet to.
That being said, the thread you linked to still had some valid reports I believe so maybe we can use this thread to deal with them:
1) "/sockudp -k SERVER" doesn't do anything, I think it should report a syntax error.
2) "/sockudp -kn SERVER" triggers on sockwrite with $sockerr set to 3 with the winsock error message: "[10047] Address family not supported by protocol family", should report a syntax error as well