tags:

views:

243

answers:

0
Q: 

NSURLConnection connectionWithRequest blocks interface

Hi all.

I thought the reason behind having asynchronous requests is to have it run in the background? Well, I'm uploading something using NSURLConnection connectionWithRequest, it all works fine. The only thing is, it results in the Beach Ball of Death and the user interface becomes unusable. Of course there's the possibility to run it in a thread and blocking that thread with a run loop, but that has a high CPU cost. Isn't there any other, proper way to do this?

Thanks, Matthias

related questions

How can I use Core Animation to interpolate property values over time on my own classes?
Opening a non-standard URL in a Cocoa app
Up-to-date libFoundation alternative
What's a good way to write a Cocoa front-end to an Erlang application?
What is the best book for learning objective-c?
Performance difference between dot notation versus method call in Objective-C
Cocoa tips for PHP developers?
What is the best way to unit test Objective-C code?
Best way to export a QTMovie with a fade-in and fade-out in the audio
NSEnumerator performance vs for loop in Cocoa
Objective-C: Passing around sets of data
How can I launch the Google Maps iPhone application from within my own native application?
What does the @ symbol represent in objective-c?
What's the difference between a string constant and a string literal?
What's a 'null defined macro'?
Any ReSharper equivalent for Xcode?
Objective-C/Cocoa: How do I accept a bad server certificate?
Drawing a view hierachy into a specific context in Cocoa
In Cocoa do you prefer NSInteger or just regular int, and why?
Cocoa - best way to capture key events in NSTextView?
How do you name your instance/param values?
Accessing iSight programatically?
Cocoa and Objective-C resources?
Understanding reference counting with Cocoa / Objective C
How-to articles for iPhone development, Objective-C