Understand disconnect in sockets

Question

0.00/5 (No votes)

See more:

Hello
I'm creating a chat application. When a user disconnects(with end proccess of app, disconnecting from network ,...) the Socket in the server is Connected=True. How i cant understand when a user disconnects without saying to server?(like yahoo messenger. when a user disconects other friends will see).

Posted 28-Dec-09 6:12am

Napster25

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)

Jimmanuel · Accepted Answer · 2009-12-28T07:30:00

Socket.Connected represents the state of the socket at the last read or write operation, not the current state of the socket. There are several different ways to handle disconnects:

1) When the client disconnects it can send a message to the server saying that it's about to disconnect.
2) Have the server use the Socket.Poll[^] method to get the current status. The return value from that can be combined with other information to determine if the socket is still open.
3) Have the server periodically send out a heartbeat message to the clients to test the connection. If it's closed then the send will fail.

Using (1) will give you instantaneous notification when a client drops and (3) will handle clients that improperly drop their connections. (3) will also keep the client aware of the socket state since it can check for the heartbeats. (2) is similar to (3) except that nothing is sent to the clients so both client and server would have to actively check the socket state.