Making recv_from function non-blocking

Question

1.00/5 (1 vote)

See more:

, +

I am working on udp server/client application. For finding out if any of the client is down, server sends a handshake message to the client. Then, the server waits for the response of client to send some data to assure that the client is active. For this the server blocks in call to recv_from() unless the client replies back, but if the client is down, the server blocks infinitely in call to recv_from. I want to implement such a functionality on my server so that it waits in call to recv_from for a specific time (say 2 secs). If no data received from the client within 2 seconds, the client is considered to be dead and recv_from returns. Is there any way to do it? I searched internet but found solutions like setting MSG_DONTWAIT flag that returns immediately when no data received, but in my case, I don't want recv_from to return immediately but wait for data for a specific duration of time, and when no data received for that specific duration, the recv_from function should retun. Any help is appreciated.

Posted 10-Apr-13 18:52pm

ayesha hassan

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2013-04-10T22:18:00

This is the wrong way to do it, you should use a non-blocking socket (see http://msdn.microsoft.com/en-us/library/windows/desktop/ms740121(v=vs.85).aspx[^]). Keep a state table for each client and whenever a message is received mark the time in the table. Check your state tables periodically and if no message has been received in less than the timeout time, mark the client as not responding.