Re: NSURLConnection's +sendAsynchronousRequest and threads
Re: NSURLConnection's +sendAsynchronousRequest and threads
- Subject: Re: NSURLConnection's +sendAsynchronousRequest and threads
- From: Jens Alfke <email@hidden>
- Date: Sat, 17 Dec 2011 16:11:05 -0800
On Dec 17, 2011, at 3:33 PM, Ryan McGann wrote: Any particular reason you care about which thread your completion block is run on?
Because it needs to access my app’s object model, which is not thread-safe. I already have the direct interaction with the object model isolated on a single thread, but it does need to send asynchronous HTTP requests and then operate on the results.
I ended up going back to the traditional approach and building a small class that implements the NSURLConnection delegate protocol. I was hoping the new API could make things easier for me, but it didn’t seem to be worth the trouble.
—Jens
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden