What is the point of a host-reachability test that doesn't test the reachability of the host?
What is the point of a host-reachability test that doesn't test the reachability of the host?
- Subject: What is the point of a host-reachability test that doesn't test the reachability of the host?
- From: G S <email@hidden>
- Date: Wed, 01 Jun 2011 17:13:58 -0700
Hi all.
I'm trying to implement some robust network-failure handling in my
iPhone app. The test of whether my host is reachable returns YES even
when connected to a router that has no Internet connection. Apple's
docs say, "A remote host is considered reachable when a data packet,
sent by an application into the network stack, can leave the local
device." And indeed this is how it behaves. You can pull the cable
out of your router, and as long as your phone is connected to it, the
host test will claim any host is reachable.
So why take an address at all? I'm using Donoho's enhancement of
Apple's Reachability example, and I don't see the difference between
the general "Internet" test (reachabilityForInternetConnection) and a
specific-host test (reachabilityWithHostName). And how are people
truly testing the availability of a host, given the bogus nature of
these results?
Thanks!
Gavin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden