Re: Detecting cable unplug/Network failure
Re: Detecting cable unplug/Network failure
- Subject: Re: Detecting cable unplug/Network failure
- From: james woodyatt <email@hidden>
- Date: Mon, 2 Mar 2009 10:31:21 -0800
On Mar 2, 2009, at 10:18, Peter Sichel wrote:
On Mar 2, 2009, at 12:27 PM, David García wrote:
I'm quite new in Mac programming, and I've found some problems
where I got stuck in the network. The matter is that, I need to
know when there's a physical network error (most immediate cable
being unplugged)....
It sounds like you want to be notified when an interface goes down
or comes back up. [...]
That will only help if the network cut is on the link directly
connected (or associated, in the 802.11 case) at the endpoint node.
If the cut happens at another L2 or L3 hop, e.g. the uplink on your
ethernet switch is disconnected, then those techniques won't work.
I mention this because I'm always suspicious when I hear application
programmers say they need to know when there's a *physical* network
error, as if it should matter to the application one way or another.
This is generally an issue for operating systems programmers, not
applications programmers.
--
james woodyatt <email@hidden>
member of technical staff, communications engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden