NSManagedObject using on specified queue
up vote
0
down vote
favorite
I have a background task that is running on background queue. I need to load some NSManagedObjects in this task. I know I need to use private context but how to bound this context to my existing background queue so I can use this NSManagedObjects in my background task? Should I perform in this background task performBlock
or performBlockAndWait
or maybe I should just call from UI Thread performBlock
on private NSManagedObjectContext
and use queue from this context to perform any background task including loading saving NSManagedObjects and other background tasks like communicating with rest-api, etc...
I'm just not sure that I can use this queue from context to do any additional tasks not related to CoreData NSManagedObjects
? If not how to use those NSManagedObjects
in queue that I created for my task?
ios core-data dispatch-queue
add a comment |
up vote
0
down vote
favorite
I have a background task that is running on background queue. I need to load some NSManagedObjects in this task. I know I need to use private context but how to bound this context to my existing background queue so I can use this NSManagedObjects in my background task? Should I perform in this background task performBlock
or performBlockAndWait
or maybe I should just call from UI Thread performBlock
on private NSManagedObjectContext
and use queue from this context to perform any background task including loading saving NSManagedObjects and other background tasks like communicating with rest-api, etc...
I'm just not sure that I can use this queue from context to do any additional tasks not related to CoreData NSManagedObjects
? If not how to use those NSManagedObjects
in queue that I created for my task?
ios core-data dispatch-queue
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a background task that is running on background queue. I need to load some NSManagedObjects in this task. I know I need to use private context but how to bound this context to my existing background queue so I can use this NSManagedObjects in my background task? Should I perform in this background task performBlock
or performBlockAndWait
or maybe I should just call from UI Thread performBlock
on private NSManagedObjectContext
and use queue from this context to perform any background task including loading saving NSManagedObjects and other background tasks like communicating with rest-api, etc...
I'm just not sure that I can use this queue from context to do any additional tasks not related to CoreData NSManagedObjects
? If not how to use those NSManagedObjects
in queue that I created for my task?
ios core-data dispatch-queue
I have a background task that is running on background queue. I need to load some NSManagedObjects in this task. I know I need to use private context but how to bound this context to my existing background queue so I can use this NSManagedObjects in my background task? Should I perform in this background task performBlock
or performBlockAndWait
or maybe I should just call from UI Thread performBlock
on private NSManagedObjectContext
and use queue from this context to perform any background task including loading saving NSManagedObjects and other background tasks like communicating with rest-api, etc...
I'm just not sure that I can use this queue from context to do any additional tasks not related to CoreData NSManagedObjects
? If not how to use those NSManagedObjects
in queue that I created for my task?
ios core-data dispatch-queue
ios core-data dispatch-queue
asked Nov 11 at 11:58
Marcin Kapusta
1,93322032
1,93322032
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Although queue management can always be tricky, queues spun by Core Data can run code like any other queues.
In particular, you can use a queue from the managed object context to do additional tasks not related to Core Data or its managed objects. When Core Data was first released on macOS in 2005, managed objects had to be accessed on the main thread, which of course could be quite busy with other tasks.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Although queue management can always be tricky, queues spun by Core Data can run code like any other queues.
In particular, you can use a queue from the managed object context to do additional tasks not related to Core Data or its managed objects. When Core Data was first released on macOS in 2005, managed objects had to be accessed on the main thread, which of course could be quite busy with other tasks.
add a comment |
up vote
0
down vote
Although queue management can always be tricky, queues spun by Core Data can run code like any other queues.
In particular, you can use a queue from the managed object context to do additional tasks not related to Core Data or its managed objects. When Core Data was first released on macOS in 2005, managed objects had to be accessed on the main thread, which of course could be quite busy with other tasks.
add a comment |
up vote
0
down vote
up vote
0
down vote
Although queue management can always be tricky, queues spun by Core Data can run code like any other queues.
In particular, you can use a queue from the managed object context to do additional tasks not related to Core Data or its managed objects. When Core Data was first released on macOS in 2005, managed objects had to be accessed on the main thread, which of course could be quite busy with other tasks.
Although queue management can always be tricky, queues spun by Core Data can run code like any other queues.
In particular, you can use a queue from the managed object context to do additional tasks not related to Core Data or its managed objects. When Core Data was first released on macOS in 2005, managed objects had to be accessed on the main thread, which of course could be quite busy with other tasks.
answered Nov 12 at 6:16
Jerry Krinock
1,5801320
1,5801320
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248501%2fnsmanagedobject-using-on-specified-queue%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown