Sockets in C#

Hi,
I have the client and Udp server communicate with each other.Now im not getting the exception "The existing connection was forcibly closed by the remote host".This is because i have defined the server in a separate project.

The client is now able to communicate with 1 server at one ip and port.But i want the client to call another udp server at another port but same ip.For eg:the client is communicating with udp server at port 10001.After every 15 secs the client should connect with the servers at different ports(10002,10003 etc)

How i can do this?Please give me your suggestions

You have to make sure the clients and the server agree to mutually close the connection. Otherwise you get an exception that it was "forced" by the other side.

This has nothing to do with C# specifically, nor does it matter where the information is defined. It is a very simple and basic tenet of socket based programming.

Quote:

---

Originally Posted by TheCPUWizard

You have to make sure the clients and the server agree to mutually close the connection. Otherwise you get an exception that it was "forced" by the other side.

This has nothing to do with C# specifically, nor does it matter where the information is defined. It is a very simple and basic tenet of socket based programming.

---

How would you go about doing this? I usually just handle the exception on the server side (and client side as well) and check the SocketException.ErrorCode property and if its the code that represents a client forcibly closing the connection I just ignore it and move on.

Its always left an eery feeling in the back of my mind though, like something isnt being finished...

You make sure "the other side" knows you are going to close the connection, so it can close it cleanly. :rolleyes:

I ran into this problem in a Silverlight application that integrates with a web service, the only problem is that if the web browser crashes or something it takes the app with it and the connection will end (forcibly close) abnormally.

I guess I dont see of any sure-fire way to make sure the server knows that the client wants to close the connection.

With sockets, that is actually a perfectly normal exception to get and it should be handled by your code. Even if you make the server and client use a graceful shutdown (using Socket.Shutdown instead of Socket.Close), you will still get this exception if there is a network error.

Ok good, thanks, lol. I was hoping someone would say that its ok. I mean, a network connection can take a crap so this exception could be propagated sometimes. It just happens...