> On Aug 14, 2015, at 7:01 PM, Ken Thomases <k...@codeweavers.com> wrote: > > On Aug 14, 2015, at 8:43 PM, Carl Hoefs <newsli...@autonomy.caltech.edu> > wrote: > > You can use a serial GCD queue for the same purpose with my above > suggestions. But even if you want to keep using an NSOperationQueue, you can > still use my first dispatch_after() suggestion. It works just like your code > except for replacing -performSelector:withObject:afterDelay: with > dispatch_after(). This changes doesn't affect anything about how > -doStatusChecks works. It will still use your NSOperationQueue. > > You don't need to use the main GCD queue for my dispatch_after() suggestion, > you can use a global concurrent queue. Either works.
Ah, yes, that's a great solution! I was considering using a second NSOperationQueue for the status recheck task, but the dispatch_after() is lightweight and a perfect fit. Many thanks, -Carl _______________________________________________ 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
