I actually think for a simple case like this one, the NSThread approach will have simpler, more straightforward code. I say go with whichever way makes more sense for your style of coding.

Luke

On May 14, 2009, at 2:56 PM, Michael Ash wrote:

On Thu, May 14, 2009 at 4:52 PM, Eric E. Dolecki <[email protected]> wrote:
Just curious, but if I am loading images into a UIImageView in table cells from online URLs, is it better to use NSThread or use async NSURLConnection
to ensure that the scrolling is smooth while images are loaded in?

I'd recommend the async method if it's at all reasonable. Threads are
difficult to write, dangerous to use, and difficult to debug. If you
can avoid them without blocking your app or causing major coding
headaches, then it's generally best to avoid them.

Mike
_______________________________________________

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/luketheh%40apple.com

This email sent to [email protected]

_______________________________________________

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]

Reply via email to