On 18 Jan 2010, at 16:37, Clint Shryock wrote: > I had the same issue in the past using NSOperationQueue and NSURLConnection, > and I resolved it by simply telling NSURLConnection to send using > synchronously using sendSynchronousRequest:returningResponse:error: > > Would that not take care of the issue?
That is no different to servicing the run loop for an 'asynchronous' operation and is generally a bad idea in the worker threads; it needlessly removes them from the worker pool until the response has arrived. Please see my previous post for alternatives. Keith _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
