Re: [twsocket] TWSocket.Close() blocks on certain machines after sending UDP

2011-07-13 Thread Merijn Bosma
On 7/13/2011 12:13, Arno Garrels wrote: Merijn Bosma wrote: Now the interesting part is that on another Windows 7 machine the call to closesocket() is not blocking. When looking with wireshark I see that the 3 arp requests are sent, but closesocket() simply does not wait for them. I'm happy you

Re: [twsocket] TWSocket.Close() blocks on certain machines after sending UDP

2011-07-13 Thread Arno Garrels
Merijn Bosma wrote: >>> Now the interesting part is that on another Windows 7 machine the >>> call to closesocket() is not blocking. When looking with wireshark I >>> see that the 3 arp requests are sent, but closesocket() simply does >>> not wait for them. >> >> I'm happy you see the same behavio

Re: [twsocket] TWSocket.Close() blocks on certain machines after sending UDP

2011-07-12 Thread Arno Garrels
Merijn Bosma wrote: > How can I confirm that this is what's happening with me? As far as I recall it was required to have a TTimer running in order to repeat this issue, very very strange. Make a simple test application and verify that line "iStatus := WSocket_Synchronized_closesocket(FHSocket);"