RE: Lost network connection detection
- From: Void <Void@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 6 Apr 2008 18:40:00 -0700
Generally, you would use TCP for any kind of connection oriented programming.
UDP is a one way ticket. The only thing i can think is pinging the server
before sending the packet. Is there a particular advantage that your looking
for that directed you to UDP?
"stgislander" wrote:
I'm forwarding this question from a retired software developer who truthfully.
is having a difficult time reading the small text on the forum.
He is sending and receiving UDP packets over a wireless network to control a
semi-autonomous model, and is trying to development a routine that can detect
when the network connection (carrier) is lost and is reestablished. Much
like the balloons that pop up over the network connection icon when the
network cable is unplugged and replugged. If he can detect this, he can
notify the program operator when lost and reset his ports when it returns.
He tells me he has tried a few methods but not seem to work well, so he is
diving back into the Winsock implementation to see if he is missing something.
What is the best way to detect a lost network connection?
- Follow-Ups:
- Re: Lost network connection detection
- From: Volodymyr M. Shcherbyna
- Re: Lost network connection detection
- References:
- Lost network connection detection
- From: stgislander
- Lost network connection detection
- Prev by Date: Wireless Zero Config
- Next by Date: Re: Small packet filter app
- Previous by thread: Lost network connection detection
- Next by thread: Re: Lost network connection detection
- Index(es):
Relevant Pages
|
