> I would add, that for a long running process, open ended work, or task, I > would favor a thread. But for short and finite items I would favor > GCD/NSOperationQueue. > > Are you going to only load one image, the next image, in this concurrent > loading scenario? Or, will you be loading many images and caching them?
No, just one (next) image. That will then get displayed about a minute later, at which point the image after that should get prefetched. > > I would imaging looking one or two ahead would be the choice. Yes, I am planning to look ahead just one image. That's why I thought a whole queue might be overdoing it for just one task that takes usually just a few milliseconds, and occasionally 1-2 seconds. But if you say that for such one-off tasks, an NSOperationQueue is better, I'll go with that approach. And thanks a lot to everybody for sharing their insights and hints. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
