More than one JobIntentService - performance vs clean code
What is the best practice for using JobIntentService
with regards to how many should there be in an application with more than one "background work areas"?
For example: if an application has a repository that needs to do some background work and some other work that is done on the network (unrelated to the database), should there be one JobIntentService
for both or one for each area?
I think two will make for a cleaner code, but will there be a performance (or other) impact from having more JobIntentServices
? Or is there a clean way to use one JobIntentService
with multiple "users"?
android android-service jobintentservice
add a comment |
What is the best practice for using JobIntentService
with regards to how many should there be in an application with more than one "background work areas"?
For example: if an application has a repository that needs to do some background work and some other work that is done on the network (unrelated to the database), should there be one JobIntentService
for both or one for each area?
I think two will make for a cleaner code, but will there be a performance (or other) impact from having more JobIntentServices
? Or is there a clean way to use one JobIntentService
with multiple "users"?
android android-service jobintentservice
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34
add a comment |
What is the best practice for using JobIntentService
with regards to how many should there be in an application with more than one "background work areas"?
For example: if an application has a repository that needs to do some background work and some other work that is done on the network (unrelated to the database), should there be one JobIntentService
for both or one for each area?
I think two will make for a cleaner code, but will there be a performance (or other) impact from having more JobIntentServices
? Or is there a clean way to use one JobIntentService
with multiple "users"?
android android-service jobintentservice
What is the best practice for using JobIntentService
with regards to how many should there be in an application with more than one "background work areas"?
For example: if an application has a repository that needs to do some background work and some other work that is done on the network (unrelated to the database), should there be one JobIntentService
for both or one for each area?
I think two will make for a cleaner code, but will there be a performance (or other) impact from having more JobIntentServices
? Or is there a clean way to use one JobIntentService
with multiple "users"?
android android-service jobintentservice
android android-service jobintentservice
asked Nov 25 '18 at 10:19
MikeLMikeL
7401622
7401622
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34
add a comment |
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34
add a comment |
0
active
oldest
votes
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%2f53466538%2fmore-than-one-jobintentservice-performance-vs-clean-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53466538%2fmore-than-one-jobintentservice-performance-vs-clean-code%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
developer.android.com/topic/libraries/architecture/workmanager/…
– pskink
Nov 25 '18 at 10:34