In this project the protocol is to:
I've noticed in the log that sometimes after the timeout we receive the ack anyway. Since the socket stays open for clean up and stragglers after the close I understand why.
But is there a better way to handle this? I'd like to be sure the connection is really down before reporting something to a line operator.
The timeout right now is an arbitrary value (2.5 seconds) tied to an external timer. It is not in the .Net TCP stack.
The TCP connection isn't really down unless the socket closes on your side. It takes minutes for TCP to decide the connection is down and close the socket if it doesn't receive any response from the network after sending data.
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments