-
Notifications
You must be signed in to change notification settings - Fork 7.3k
UDP packet loss #6696
Comments
Just for future reference, seems to be working fine on unixes. |
It looks like windows is just discarding the rest of them. @piscisaureus may I ask you to take a look at this? I have no time to work on windows stuff, but if you won't find time either - I'll look into it in a month... |
@gagle Have you tried this on latest v0.11? |
@trevnorris Yes, same results. The client only receives 7 packets. |
Shifted it to v0.13 milestone. |
My 2 cents Works fine too on Windows 8.1 & NodeJS v0.11.10 c:\temp>node client.js
c:\temp>node server.js
|
Guess it is won't fix |
@orangemocha .. Something you can help with? |
I can definitely investigate, but not for some time. Stuff on my plate is piling up faster than I can fix it lately. |
I got the same problem on Linux ... I use the UDP multi/unicast to manage heartbeats between servers and sometime w/o any really reasons i lose "connection" while the HB timeout is very high (about 10 seconds), the HB packet interval is 500ms and for long time i got some packets dropped.
You can find my source code there https://github.com/binarysec/gate/blob/master/src/lib/acn/js/service.js and the doc there https://github.com/binarysec/gate/wiki/AssociativeCacheNetwork |
@mykiimike Thanks for source that doesn't depend on any external modules. Have you tried running this on latest v0.11? |
@trevnorris no but i can/will try it Monday. |
Node v0.10.22
Windows 7 x64
The UDP socket (as a client) doesn't return all the packets that the server sends in this scenario:
The following example does:
Note: If the server sends less than 7 packets each time, the client receives all the blocks. If the server sends more than 6 packets BUT you change the size of each of them (e.g. 10 bytes) the client receives all the blocks.
Server:
Client:
RESULT
Client:
Server:
The text was updated successfully, but these errors were encountered: