NSManagedObject using on specified 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
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
add a comment |
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
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
add a comment |
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
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
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 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
asked Nov 11 '18 at 11:58
Marcin KapustaMarcin Kapusta
1,97822234
1,97822234
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
add a comment |
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 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
add a comment |
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 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
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 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
answered Nov 12 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
answered Nov 12 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
answered Nov 12 '18 at 6:16
Jerry KrinockJerry Krinock
1,5921520
1,5921520
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.
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
