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.
In my C++ application I’m using the recv function in a loop.
I want to identify a network connection issue by getting a negative value from recv function.
The one thing I can see in my tests is that when I’m getting off the network cable, I can wait for ~minute till I can see that my application got this negative value.
Do you know what is the time duration for the C++ code to know that a network connection issue occur? Can I manage this time?
There’s no sane way of doing this on the TCP-only level. The option that was intended for this is
SO_KEEPALIVE, but it’s pretty useless.Implement application-level heartbeats and mark the socket disconnected when no data or heartbeat was received within specified time (this pretty much assumes non-blocking mode, or at least a
select(2)loop with timeout).