After the connection has been established, and the two sides have no communication, which timeout value determines the idle connection be closed?
After the connection has been established, and the two sides have no communication, which
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After the connection has been established, and the two sides have no communication, which timeout value determines the idle connection be closed?
In general, none. It is the programmer’s and protocol-designer’s responsibility to specify, implement and enforce any timeouts at an application level.
However, all kinds of things can happen to cause outages and other network connectivity issues. It is not possible to determine if a TCP connection is idle, or if the other end is unreachable, unless you’re trying to send something.
For this reason, most servers with long-standing connections contain simple polls such as sending empty packets or such every so-often just to detect lack of connectivity.