On May 20, 2009, at 2:03 PM, Eric Hermanson wrote:
I think that's precisely my point. If I have to manage the data transfer mechanism independently of the Reachability APIs in the first place, then that was why I asked the question, why use the Reachability APIs at all? I guess that was the basis for my original post. Sure, Reachability is a nice thing to have to notify me in a general sense if a given network MAY be reachable (such that I can update a UI status element), but beyond that, for actually transferring a boat load of data back/forth (which is what my app does), I pretty much have to handle network outage, reconnect logic, and IOException/EOF myself (as one would expect). I think anyone would have to handle these things. Hence my original question. Thank you for your thoughts.
Without Reachability, you'd need to start by polling connect() until it succeeded. Polling is bad. Reachability can tell you "there is no network, don't bother trying to connect" and "there's a network now, try connecting".
Of course, you still need to handle errors any time after that, and need to use different techniques to avoid polling and main-thread blocking. Reachability only helps with the part before connect() succeeds.
-- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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
