RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
Indeed, just a static call.
That was me writing in C# style before :sweat_smile:
public class App {
private Observer<Observable<Integer>> ob;
public App() {
PublishSubject<Observable<Integer>> sub = PublishSubject.create();
rx.Observable.merge(sub, 10).subscribe(System.out::println);
ob = sub;
}
public void put(Observable<Integer> t) {
ob.onNext(t);
}
public static void main(String[] args) {
App app = new App();
Observable.range(1, 100).subscribe(integer -> {
app.put(Observable.just(integer));
});
}
}
That works for me
public class App {
private Observer<Observable<Integer>> ob;
public App() {
PublishSubject<Observable<Integer>> sub = PublishSubject.create();
rx.Observable.merge(sub).buffer(10).subscribe(System.out::println);
ob = sub;
}
public void put(Observable<Integer> t) {
ob.onNext(t);
}
public static void main(String[] args) {
App app = new App();
Observable.range(1, 100).subscribe(integer -> {
app.put(Observable.just(integer));
});
}
}
Works also
observe how i kept the subject as hidden as possible in my snipped
This case we had here is pretty much the only one where i dont know how to avoid the subject.
@mattblang I haven't used IRC in years I guess I'll find a new client :D
This is really good stuff .. covers almost everything in Rx with examples on where to use https://github.com/Froussios/Intro-To-RxJava
Hello, everyone.
Can someone please explain why do the following two snippets of code behave differently?
Observable.<Boolean>create(subscriber -> Observable.just(true).subscribe(subscriber))
.flatMap(
b -> Observable.<Integer>create(subscriber -> {
subscriber.onNext(1);
subscriber.onCompleted();
}).subscribeOn(Schedulers.io()) // to imitate async request
)
.subscribe(System.out::println);Observable.<Boolean>create(subscriber -> Observable.just(true).subscribe(subscriber::onNext, subscriber::onError, subscriber::onCompleted))
.flatMap(
b -> Observable.<Integer>create(subscriber -> {
subscriber.onNext(1);
subscriber.onCompleted();
}).subscribeOn(Schedulers.io()) // to imitate async request
)
.subscribe(System.out::println);When I run the first one it doesn’t print anything to the console, but the second one prints 1 as expected.
@yesenarman your first example has a race condition. When your observable chain subscribes to the subscribeOn operator a new thread on the io scheduler subscribes upward to the flatmap but your main thread returns from the subscribe and terminates the program. hence why you don't see it print. The other thread hasn't onNexted yet.
you can fix the race condition by using a TestSubscriber and calling awaitTerminalEventAndUnsubscribeOnTimeout(int, TimeUnit) or simply adding a countdown latch and awaiting after your subscribe
Hi. Is there an equivalent to
delaySubscription but for unsubscription? I'd like to be able to have the subscriber be effectively unsubscribed, but the observable should not be unsubscribed immediately (and sent data should be sent to oblivion). Use case: a GPS observable that takes time to acquire a fix initially that is share()d. A delayed unsubscription would let the GPS active for a few seconds in case another subscriber gets interested fast enough. I guess that could be a variant of refCount() too, that would take a delay before unsubscribing.
(I cooked up an operator for doing this if anyone is interested: https://gist.github.com/samueltardieu/12db44dc01340f22e9da)
(I can use it as
newObservable = observable.share().lift(new DelayedUnsubscription(5, TimeUnit.SECONDS)), and I then subscribe to newObservable)
@wKovacs64 I answered that on stack overflow a while back. See http://stackoverflow.com/questions/31733455/rxjava-observable-cache-invalidate/31738646#31738646
does anybody know what effect
onNext will have on a PublishSubject after PublishSubject#onCompleted has been called?
will the
onNext item be emitted, will it fail to be emitted silently, or will the call fail with an exception?