Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
1) what is happening when we add NSOperation or NSInvocationOperation in NSoperationQueue?
2) What is the difference between NSoperation and NSInvocationOperation?
3) which one is the best ?
1. Difference Between NSoperation and NSInvocationOperation
An NSoperation object is a single-shot object—that is, it executes its task once and cannot be used to execute it again.
The NSInvocationOperation class is a concrete subclass of NSOperation that manages the execution of a single encapsulated task specified as an invocation. You can use this class to initiate an operation that consists of invoking a selector on a specified object. This class implements a non-concurrent operation.
2.What is happening when we add NSOperation or NSInvocationOperation in NSoperationQueue
You typically execute operations by adding them to an operation queue (an instance of the NSOperationQueue class). An operation queue executes its operations either directly, by running them on secondary threads, or indirectly using the libdispatch library (also known as Grand Central Dispatch)
3.Which one is the best
I think the word Best may vary as per your situations 🙂