True. But the situation we were running into was that a server might not be up and I could tell faster with ping than a timer.
-----Original Message----- From: David Duncan [mailto:[email protected]] Sent: Thursday, June 02, 2011 1:37 PM To: Jim Adams Cc: 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 10:31 AM, Jim Adams wrote: > 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. If you want to create your own timeout, all you should have to do is start the (asynchronous) connection and set a timer for the timeout length you desire. If you don't get a response by then (presumably you just cancel the timer if you do) then you cancel the connection attempt and declare that the connection timed out. No need for additional connections. -- David Duncan _______________________________________________ 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]
