NSOperations and iOS architecture questions -


I'm getting deep in the stuff and I have a question from the IOS architecture:

* 1. Is it possible to kill my NSOperations / NSOperationsQueue in the iOS system architecture?

* 2. What can be done to do this? What kind of situation?

* 3IOS is running on low resources and is init'ed with the NSOption queue allocated and new NSOperations queued?

* 4 As I read about the NSOperation - they can not run until they achieve the isReady = YES to execute , Or isReady = NO , if still there are still incomplete operations on which it depends. What kind of dependent job can this be?

1) No, it will not work until it hits your entire application. In this case, You will be notified with the - (zero) app. Device: (UIApplication *) application in your app

2) N / A

3) This one

4) Operation queue will process all your NSOperations. NSOperations dependencies are only for you to be equal to "IsReady", you will need to manually change the value.

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -