I have not a lot of Cocoa experience here, so I am legitimately asking this question, no snark intended: what’s the advantage to building a home-made “serial” “queue” as opposed to just using an actual serial operation queue? Haven’t you just described the first few steps one would take were one to set out to reimplement NSOperationQueue?
FWIW (and as I mentioned, I am an eminently ignorable person when it comes to Cocoa expertise), I sort of see the essence of the “async” flavor of NSOperation as being to provide definitive signaling when an otherwise asynchronous operation is really “finished“ — for whatever business definition of “finished” one requires. So I don’t completely agree that this would be “shoehorning”; seems right on the money to me. Just one opinion! Cheers, Peter On Jun 28, 2016, at 6:50 PM, "Gary L. Wade" <garyw...@desisoftsystems.com> wrote: > Based on his desire to do this serially, he would need a serial queue, and > he's using asynchronous requests, so succeeding calls from his completion > handler with a simple array in queue pattern is simpler than shoehorning it > all into dispatch queues. > -- > Gary L. Wade (Sent from my iPhone) > http://www.garywade.com/ > >> On Jun 28, 2016, at 3:45 PM, Alex Zavatone <z...@mac.com> wrote: >> >> Would a dispatch queue get what he's looking for? _______________________________________________ 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
