//with s being a PublishSubject<String> or <URL>, and download() returning a status somehow final Scheduler singleScheduler = Schedulers.from(Executors.newSingleThreadExecutor()); s .subscribeOn(singleScheduler) .map(s -> download(s)) .observeOn(AndroidSchedulers.mainThread()) .subscribe(status -> showStatusInUI(status));
Observable[SomeArgs]flatMapped with the
Observable.from(httpResponseFuture)(RxScala, but details shouldn't be important here)
requestwith a sane amount that Netty will be able to cope with?
subscribeOnthread -- it's being handled inside a DrmManagerClient event handler thread
subscribeOnscheduler (in this example,
Schedulers.io)? If so, what is the best way to do that?
@RobWin Maybe I should use different wording than short-circuit. Basically, I just want to end a series of calls in a flatMap if an Exception happens. See this SO ticket, I detailed my issue with a sample.
.onErrorResumeNextwould be a function that unwraps the Exception and returns a new Observable, which you would create with
flatmapwill be serialized, not parallelized
.paralleloperator in RxJava but they removed it because its behavior was confusing
Schedulers.trampolineto schedule some work in the flatmap function, and then return thread execution to the original