Re: async NSOperation and NSOperationQueue
Re: async NSOperation and NSOperationQueue
- Subject: Re: async NSOperation and NSOperationQueue
- From: Jason Coco <email@hidden>
- Date: Fri, 19 Sep 2008 18:48:16 -0400
On Sep 19, 2008, at 18:27 , Michael Ash wrote:
On Fri, Sep 19, 2008 at 2:41 PM, John Love <email@hidden>
wrote:
Michael Ash wrote:
Has it occurred to you that waiting for the operation to finish is
rather at odds with the idea of trying to run it asynchronously to
keep your program responsive?
Absolutely, but if the Thread is running in the background, it really
shouldn't matter to the main Thread of the app. While calculations
of a
document are buzzing away in the background, I could be doing other
things,
e.g., opening other docs to get their calculations going. But, I
cannot get
back control until after the first document's calculations are done.
I'm confused. I thought that the call to [theQueue
waitUntilAllOperationsAreFinished] was being made on the main thread.
If you're already spawning a second thread for those calls, why bother
with the NSOperationQueue at all?
That's how I read it too...
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden