Sign in to follow this  

[.net] TcpClient rules

Recommended Posts

I once asked this sort of question to the networking gurus at a game shop.
Basically, they said that if this happens then there are bigger problems to worry about.

In essence the answer became, catch an exception (probably a to this effect and try to establish the connection again, or wait for the connection to re-establish from the client.

There are like 60 possible lame situations that can happen to cause problems across the network, and it is hard to make it a reliable connection.

But, if you really want to is a test you might try

write an app that sends data across the wire
send a small amount of data
sleep for a little bit
until done
then pull the network cable and plug it back in.

As a side note, tcp is supposed to garuntee a packet is received, like you said, resending packets and such.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this