Prevent multiple calls to the method using rxjava
up vote
0
down vote
favorite
There are two events - event1
and event2
which can call getA()
, these two events could occur simultaneously and trigger getA
. I don't want to call getA
multiple times until it gets done. I am using isDisposed()
to check if its still active and calling dispose()
explicitly in doFinally
and setting fetchADisposable as null . Is there a better way to do this ?
Disposable fetchADisposable;
public void getA() {
fetchA() //returns Observable
.doFinally(new Action() {
fetchADisposable.dispose();
fetchADisposable = null;
}).subscribe() {
@Override
public void onSubscribe (Disposable d){
fetchADisposable = d;
}
@Override
public void onNext () {
}
@Override
public void onError (Throwable e){
}
@Override
public void onComplete () {
}
}
}
public void event1() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
public void event2() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
rx-java rx-java2 rx-javafx
New contributor
add a comment |
up vote
0
down vote
favorite
There are two events - event1
and event2
which can call getA()
, these two events could occur simultaneously and trigger getA
. I don't want to call getA
multiple times until it gets done. I am using isDisposed()
to check if its still active and calling dispose()
explicitly in doFinally
and setting fetchADisposable as null . Is there a better way to do this ?
Disposable fetchADisposable;
public void getA() {
fetchA() //returns Observable
.doFinally(new Action() {
fetchADisposable.dispose();
fetchADisposable = null;
}).subscribe() {
@Override
public void onSubscribe (Disposable d){
fetchADisposable = d;
}
@Override
public void onNext () {
}
@Override
public void onError (Throwable e){
}
@Override
public void onComplete () {
}
}
}
public void event1() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
public void event2() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
rx-java rx-java2 rx-javafx
New contributor
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
There are two events - event1
and event2
which can call getA()
, these two events could occur simultaneously and trigger getA
. I don't want to call getA
multiple times until it gets done. I am using isDisposed()
to check if its still active and calling dispose()
explicitly in doFinally
and setting fetchADisposable as null . Is there a better way to do this ?
Disposable fetchADisposable;
public void getA() {
fetchA() //returns Observable
.doFinally(new Action() {
fetchADisposable.dispose();
fetchADisposable = null;
}).subscribe() {
@Override
public void onSubscribe (Disposable d){
fetchADisposable = d;
}
@Override
public void onNext () {
}
@Override
public void onError (Throwable e){
}
@Override
public void onComplete () {
}
}
}
public void event1() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
public void event2() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
rx-java rx-java2 rx-javafx
New contributor
There are two events - event1
and event2
which can call getA()
, these two events could occur simultaneously and trigger getA
. I don't want to call getA
multiple times until it gets done. I am using isDisposed()
to check if its still active and calling dispose()
explicitly in doFinally
and setting fetchADisposable as null . Is there a better way to do this ?
Disposable fetchADisposable;
public void getA() {
fetchA() //returns Observable
.doFinally(new Action() {
fetchADisposable.dispose();
fetchADisposable = null;
}).subscribe() {
@Override
public void onSubscribe (Disposable d){
fetchADisposable = d;
}
@Override
public void onNext () {
}
@Override
public void onError (Throwable e){
}
@Override
public void onComplete () {
}
}
}
public void event1() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
public void event2() {
if (fetchADisposable == null || fetchADisposable.isDisposed()) {
getA();
}
}
rx-java rx-java2 rx-javafx
rx-java rx-java2 rx-javafx
New contributor
New contributor
New contributor
asked Nov 20 at 23:55
Android Developer
1
1
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Your existing solution has race conditions. You really need queuing to take place so that the events are processed serially.
The serialization of processing can be done using a PublishSubject
that is subscribed to once only (say in the constructor or in an initializer method). The code looks like:
final PublishSubject<Integer> subject = createSubject();
private static PublishSubject<Integer> createSubject() {
PublishSubject<Integer> subject = PublishSubject.<Integer>create().serialized();
subject.subscribe(subscriber);
}
public void getA() {
subject.onNext(1);
}
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Your existing solution has race conditions. You really need queuing to take place so that the events are processed serially.
The serialization of processing can be done using a PublishSubject
that is subscribed to once only (say in the constructor or in an initializer method). The code looks like:
final PublishSubject<Integer> subject = createSubject();
private static PublishSubject<Integer> createSubject() {
PublishSubject<Integer> subject = PublishSubject.<Integer>create().serialized();
subject.subscribe(subscriber);
}
public void getA() {
subject.onNext(1);
}
add a comment |
up vote
1
down vote
Your existing solution has race conditions. You really need queuing to take place so that the events are processed serially.
The serialization of processing can be done using a PublishSubject
that is subscribed to once only (say in the constructor or in an initializer method). The code looks like:
final PublishSubject<Integer> subject = createSubject();
private static PublishSubject<Integer> createSubject() {
PublishSubject<Integer> subject = PublishSubject.<Integer>create().serialized();
subject.subscribe(subscriber);
}
public void getA() {
subject.onNext(1);
}
add a comment |
up vote
1
down vote
up vote
1
down vote
Your existing solution has race conditions. You really need queuing to take place so that the events are processed serially.
The serialization of processing can be done using a PublishSubject
that is subscribed to once only (say in the constructor or in an initializer method). The code looks like:
final PublishSubject<Integer> subject = createSubject();
private static PublishSubject<Integer> createSubject() {
PublishSubject<Integer> subject = PublishSubject.<Integer>create().serialized();
subject.subscribe(subscriber);
}
public void getA() {
subject.onNext(1);
}
Your existing solution has race conditions. You really need queuing to take place so that the events are processed serially.
The serialization of processing can be done using a PublishSubject
that is subscribed to once only (say in the constructor or in an initializer method). The code looks like:
final PublishSubject<Integer> subject = createSubject();
private static PublishSubject<Integer> createSubject() {
PublishSubject<Integer> subject = PublishSubject.<Integer>create().serialized();
subject.subscribe(subscriber);
}
public void getA() {
subject.onNext(1);
}
answered Nov 21 at 1:15
Dave Moten
10k12735
10k12735
add a comment |
add a comment |
Android Developer is a new contributor. Be nice, and check out our Code of Conduct.
Android Developer is a new contributor. Be nice, and check out our Code of Conduct.
Android Developer is a new contributor. Be nice, and check out our Code of Conduct.
Android Developer is a new contributor. Be nice, and check out our Code of Conduct.
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%2f53403375%2fprevent-multiple-calls-to-the-method-using-rxjava%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