Threads would be unnecessary hassle and probably slower performing.
NSURLConnection maintains its own private thread for performing the
work of all open URL connections, even if you are using the
synchronous API. By using NSThread, you are just bringing an extra
unnecessary thread into the mix (possibly more if you're planning 1
thread per-image) and then have to co-ordinate between it and the main
thread. The async NSURLConnection API takes care of that for you
already.
The only possible performance bottleneck that a thread might benefit
you is turning the downloaded image data into a UIImage. If you find
that is being slow, then maybe consider a thread-based solution for
that portion of the work.
Mike.
On 14 May 2009, at 21:52, Eric E. Dolecki 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?
Eric
_______________________________________________
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/cocoadev%40mikeabdullah.net
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]
