On Jun 2, 2011, at 11:16 AM, Nathan Sims wrote: > On Jun 2, 2011, at 10:36 AM, David Duncan wrote: > >> 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. > > This is just what I was looking for. What method/API do you use to cancel a > connection attempt?
-[NSURLConnection cancel] -- David Duncan _______________________________________________ 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
