If the NSURLConnection in question has been started asynchronously, your described scenario sounds appropriate. In fact, it's what Apple recommends since the class will handle things in the background and only report back on progress. A synchronous request would fall into the questionable realm. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/
> On Jul 14, 2015, at 8:27 AM, Alex Zavatone <z...@mac.com> wrote: > > I'm looking at some Cocoa spaghetti that seems to violate all the laws or > reason and I'd just appreciate some verification that "there is no reason > whatsoever that a sane Cocoa developer would ever do this" before I go and > change this code. > > Am I correct in assuming that there is no rational reason why a sane person > would force an NSURLRequest and NSURLConnection to run on the main thread > with a dispatch_sync for an operation that should not block the UI and > doesn't need to be sync? > > Why would someone force an NSURLConnection to run on the main thread? > > My brain hurts looking at this. > > It's too early in the day to want a third cup of coffee. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
