Why? Because the timeout was inordinately long with no way to shorten it other than create my own timeout. Users want responsiveness. One of the things I hate more than anything is when an app won't start because it can't contact its host. Its bad enough if it can contact the host but the response is really slow.
-----Original Message----- From: Kyle Sluder [mailto:[email protected]] Sent: Thursday, June 02, 2011 11:17 AM To: Jim Adams Cc: Greg Parker; G S; cocoa-dev Subject: Re: What is the point of a host-reachability test that doesn't test the reachability of the host? On Jun 2, 2011, at 6:04 AM, Jim Adams <[email protected]> wrote: > In a recent app I wrote I used the Reachability API but then when attempting > to log on to my host I pinged 5 tries at the same time as attempting to log > on. My thinking was that I could either wait the very long time for the logon > attempt to time out or I could decide after 5 failed ping attempts that the > host was down. Why? Just try to connect. If it fails, put up an error. Why does everyone insist on using roundabout ways to detect if maybe a host will accept connections on a completely unrelated port? --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
