On Wed, Apr 22, 2009 at 10:21 PM, Kyle Sluder <kyle.slu...@gmail.com> wrote: > On Wed, Apr 22, 2009 at 10:08 PM, Chris Hanson <c...@me.com> wrote: >> And instead of checking network connectivity, your application should just >> try to use the network and fail gracefully when it's not available. After >> all, it could go away between when you check and actually start using it, or >> while you're using it - at that point, what does checking get you? > > Avoidance of a timeout, perhaps? Checking reachability might spare > your user a 5 to 10 second "trying to contact server" spinning > progress indicator. That 5 to 10 seconds could instead be spent > smacking oneself for forgetting to turn on AirPort.
Any half-competent network code will error immediately in that situation, not time out. Any situation where network code will time out is also a time when reachability will either also time out or will return a false positive. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
