NSURLConnection does this as well. The main issue i had with using an
NSOperation/OperationQueue was that is was "serial" ... using the
NSURLConnection allowed me to handle MULTIPLE asynchronous downloads
which, when used with properties allowed near instantaneous UI updates.
With the NSOperation avenue, it took longer, UI updates were not as
fast as the queue would handle only one operation at a time, in series.
For me, the NSURLConnection route was just better for my specific
needs and, i think may be as well for the OP.
jack
On Mar 21, 2010, at 1:53 PM, WT wrote:
On Mar 21, 2010, at 6:25 PM, Jack Carbaugh wrote:
You don't need to overcomplicate downloading the images with an
NSOperation.
In my experience, downloading asynchronously with an
NSURLConnection and the delegate methods works far better.
Jack
I don't think using NSOperation is overcomplicating things. It's
entirely trivial to use it and, as far as I know, NSOperationQueue
takes care of scheduling the threads to make the best use of the
resources available.
W.=
_______________________________________________
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
