Mixing
What thread will be used when calling subscribeOn inside flatMapCompletable?
I have a completable that I create like so:
public class Params {
// Contains input parameters
}
public Completable startSomething(Params params) {
return Completable
.fromRunnable(() -> someMainThreadThing(params))
.subscribeOn(this.schedulers.mainThread());
}
Now, I have a source providing a Single<Params>. This is provided as part of the API, so the current thread is unknown at subscribe time. This usage looks something like this:
public Completable doSomethingWithParams(Single<Params> params) {
// Do something with the params
}
I would like to implement doSomethingWithParams like so:
public Completable doSomethingWithParams(Single<Params> params) {
return params.flatMapCompletable(::startSomething);
}
My question is, is someMainThreadThing guaranteed to be executed on the main thread, or can the setup of the Single<Params> influence the thread it is executed on?
java rx-java
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
add a comment |
I have a completable that I create like so:
public class Params {
// Contains input parameters
}
public Completable startSomething(Params params) {
return Completable
.fromRunnable(() -> someMainThreadThing(params))
.subscribeOn(this.schedulers.mainThread());
}
Now, I have a source providing a Single<Params>. This is provided as part of the API, so the current thread is unknown at subscribe time. This usage looks something like this:
public Completable doSomethingWithParams(Single<Params> params) {
// Do something with the params
}
I would like to implement doSomethingWithParams like so:
public Completable doSomethingWithParams(Single<Params> params) {
return params.flatMapCompletable(::startSomething);
}
My question is, is someMainThreadThing guaranteed to be executed on the main thread, or can the setup of the Single<Params> influence the thread it is executed on?
java rx-java
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
Yes, this setup guaranteessomeMainThreadThingruns on the main thread and completes there too because ofsubscribeOnapplied to the innerCompletable.
– akarnokd
Nov 20 '18 at 9:22
add a comment |
I have a completable that I create like so:
public class Params {
// Contains input parameters
}
public Completable startSomething(Params params) {
return Completable
.fromRunnable(() -> someMainThreadThing(params))
.subscribeOn(this.schedulers.mainThread());
}
Now, I have a source providing a Single<Params>. This is provided as part of the API, so the current thread is unknown at subscribe time. This usage looks something like this:
public Completable doSomethingWithParams(Single<Params> params) {
// Do something with the params
}
I would like to implement doSomethingWithParams like so:
public Completable doSomethingWithParams(Single<Params> params) {
return params.flatMapCompletable(::startSomething);
}
My question is, is someMainThreadThing guaranteed to be executed on the main thread, or can the setup of the Single<Params> influence the thread it is executed on?
java rx-java
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
I have a completable that I create like so:
public class Params {
// Contains input parameters
}
public Completable startSomething(Params params) {
return Completable
.fromRunnable(() -> someMainThreadThing(params))
.subscribeOn(this.schedulers.mainThread());
}
Now, I have a source providing a Single<Params>. This is provided as part of the API, so the current thread is unknown at subscribe time. This usage looks something like this:
public Completable doSomethingWithParams(Single<Params> params) {
// Do something with the params
}
I would like to implement doSomethingWithParams like so:
public Completable doSomethingWithParams(Single<Params> params) {
return params.flatMapCompletable(::startSomething);
}
My question is, is someMainThreadThing guaranteed to be executed on the main thread, or can the setup of the Single<Params> influence the thread it is executed on?
java rx-java
java rx-java
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
asked Nov 20 '18 at 0:20
MaxMax
7,71074788
7,71074788
Yes, this setup guaranteessomeMainThreadThingruns on the main thread and completes there too because ofsubscribeOnapplied to the innerCompletable.
– akarnokd
Nov 20 '18 at 9:22
add a comment |
Yes, this setup guaranteessomeMainThreadThingruns on the main thread and completes there too because ofsubscribeOnapplied to the innerCompletable.
– akarnokd
Nov 20 '18 at 9:22
Yes, this setup guarantees
someMainThreadThing runs on the main thread and completes there too because of subscribeOn applied to the inner Completable.– akarnokd
Nov 20 '18 at 9:22
Yes, this setup guarantees
someMainThreadThing runs on the main thread and completes there too because of subscribeOn applied to the inner Completable.– akarnokd
Nov 20 '18 at 9:22
add a comment |
1 Answer
1
active
oldest
votes
According to documentation Single.flatMapCompletable()
flatMapCompletable does not operate by default on a particular Scheduler.
That means that completable with startSomething() will be invoked on the same scheduler (thread) as previous chain actions if you don't call explicitly switching between schedulers.
To switch between schedulers you can use observeOn() operator. In your case reactive chain could look like
Single.fromCallable(getParams())
.subscribeOn(Schedulers.io())
.observeOn(this.schedulers.mainThread())
.flatMapCompletable(::startSomething)
In that case subscribeOn() make executing getParams() on Schedulers.io(), after that observeOn() switches to main thread and execute startSomething() on it.
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
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%2f53384498%2fwhat-thread-will-be-used-when-calling-subscribeon-inside-flatmapcompletable%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
According to documentation Single.flatMapCompletable()
flatMapCompletable does not operate by default on a particular Scheduler.
That means that completable with startSomething() will be invoked on the same scheduler (thread) as previous chain actions if you don't call explicitly switching between schedulers.
To switch between schedulers you can use observeOn() operator. In your case reactive chain could look like
Single.fromCallable(getParams())
.subscribeOn(Schedulers.io())
.observeOn(this.schedulers.mainThread())
.flatMapCompletable(::startSomething)
In that case subscribeOn() make executing getParams() on Schedulers.io(), after that observeOn() switches to main thread and execute startSomething() on it.
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
add a comment |
According to documentation Single.flatMapCompletable()
flatMapCompletable does not operate by default on a particular Scheduler.
That means that completable with startSomething() will be invoked on the same scheduler (thread) as previous chain actions if you don't call explicitly switching between schedulers.
To switch between schedulers you can use observeOn() operator. In your case reactive chain could look like
Single.fromCallable(getParams())
.subscribeOn(Schedulers.io())
.observeOn(this.schedulers.mainThread())
.flatMapCompletable(::startSomething)
In that case subscribeOn() make executing getParams() on Schedulers.io(), after that observeOn() switches to main thread and execute startSomething() on it.
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
add a comment |
According to documentation Single.flatMapCompletable()
flatMapCompletable does not operate by default on a particular Scheduler.
That means that completable with startSomething() will be invoked on the same scheduler (thread) as previous chain actions if you don't call explicitly switching between schedulers.
To switch between schedulers you can use observeOn() operator. In your case reactive chain could look like
Single.fromCallable(getParams())
.subscribeOn(Schedulers.io())
.observeOn(this.schedulers.mainThread())
.flatMapCompletable(::startSomething)
In that case subscribeOn() make executing getParams() on Schedulers.io(), after that observeOn() switches to main thread and execute startSomething() on it.
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
According to documentation Single.flatMapCompletable()
flatMapCompletable does not operate by default on a particular Scheduler.
That means that completable with startSomething() will be invoked on the same scheduler (thread) as previous chain actions if you don't call explicitly switching between schedulers.
To switch between schedulers you can use observeOn() operator. In your case reactive chain could look like
Single.fromCallable(getParams())
.subscribeOn(Schedulers.io())
.observeOn(this.schedulers.mainThread())
.flatMapCompletable(::startSomething)
In that case subscribeOn() make executing getParams() on Schedulers.io(), after that observeOn() switches to main thread and execute startSomething() on it.
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
answered Nov 20 '18 at 6:34
ConstOrVarConstOrVar
1,034149
1,034149
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%2f53384498%2fwhat-thread-will-be-used-when-calling-subscribeon-inside-flatmapcompletable%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
Yes, this setup guarantees
someMainThreadThingruns on the main thread and completes there too because ofsubscribeOnapplied to the innerCompletable.– akarnokd
Nov 20 '18 at 9:22