Yes I brought this up because many times network people will tell developers to implement a Ping Pong scheme because "nothing is wrong with the hallowed network". When the real answer is always "the network is unstable, please keep working to fix it"
The most common root cause of this type issue is, a router or switch resets due to signal failures.
Off-topic though. Ping-pong isn't necessarily used for checking network status. E.g. measure the delay, "let me know you are not dead", etc. Maybe it's my fault to use the name ping-pong but not "echo" so someone can nitpick.
The socket send receive cycle is enough to determine latency. However the protocol should be ICMP for best results because the Tcp/Ip retry logic gets in the way. Ping runs at ICMP layer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes I brought this up because many times network people will tell developers to implement a Ping Pong scheme because "nothing is wrong with the hallowed network". When the real answer is always "the network is unstable, please keep working to fix it"
The most common root cause of this type issue is, a router or switch resets due to signal failures.
Off-topic though. Ping-pong isn't necessarily used for checking network status. E.g. measure the delay, "let me know you are not dead", etc. Maybe it's my fault to use the name ping-pong but not "echo" so someone can nitpick.
The socket send receive cycle is enough to determine latency. However the protocol should be ICMP for best results because the Tcp/Ip retry logic gets in the way. Ping runs at ICMP layer.