On 9 Feb 2010, at 22:18, Laurent Daudelin wrote: >> Try using the synchronous version of NSURLConnection […]
No, don't do this. This method simply creates a private NSURLConnection delegate and enters the run loop until completion or failure. This ties the NSOperation worker thread up until completion which may shift thread ramp up costs onto other parts of you application. Instead you should create a 'concurrent' NSOperation as described in the documentation, and schedule your NSURLConnection on +[NSRunLoop mainRunLoop]. This will allow your NSOperation -start method to exit immediately and the thread to return to the pool. Keith_______________________________________________ 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
