Re: Concurrent NSOperation
Re: Concurrent NSOperation
- Subject: Re: Concurrent NSOperation
- From: Keith Duncan <email@hidden>
- Date: Thu, 22 Nov 2007 11:48:22 +0000
So, basically, for simple asychronous behavior just subclass
NSOperation and override -main. NSOperationQueue will be responsible
for creating the threading "environment", within the parameters set
(e.g. -setMaxConcurrentOperationCount:).
OK, but how will I mark the operation as still executing and
unfinished until the notification is posted?
Are the docs stating that concurrent operations MUST override
isExceuting and isFinished etc, but that non-concurrent ones can if
they so choose?
I do understand the difference between a concurrent and a non-
concurrent operation, but I also think that the use of the word
"concurrent" in a context where threads are being used will lead to
confusion. I think I'm going to file a bug on that one.
- Keith
_______________________________________________
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