Add option to change or remove default Rx scheduler
See original GitHub issueThere are few problems with setting subscribeOn(Schedulers.io())
by default:
- User can not change this behavior.
- If user adds
subscribeOn()
to already configured observable — he just adds unnecessary work to the Rx chain because it’ll switch to user thread and then switch to our initial setting —Schedulers.io()
anyway. - Some combinations of StorIO Observables may cause deadlocks because of transactions + forced multithreading (not a bug).
This is incompatible change so I am moving it to v2.0.0
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Overriding RxAndroid Schedulers in RxJava 2 - Medium
RxAndroid now supports RxJava 2, and with it, a new set of APIs for overriding Schedulers. In this post, I'll explain these APIs, ......
Read more >Choosing 'default' Schedulers for my Observable extension ...
Consider passing a specific scheduler to concurrency introducing operators Rather than using the ObserveOn operator to change the execution ...
Read more >Scheduler - ReactiveX
The SubscribeOn operator changes this behavior by specifying a different Scheduler on which the Observable should operate.
Read more >Scheduling and threading - Intro to Rx
We perform the subscription on a new thread and ensure that as we receive Customer notifications, we add them to the Customers collection...
Read more >Breaking Changes in Version 7 - RxJS
To workaround this issue there are two things you can do: 1. Rewrite your operators as outlined in the documentation, such that they...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree that it will be a way better - add an ability to configure default scheduler without breaking api. We just need to correct issue name.
Thanks man 😃
On Thu, 19 May 2016, 02:07 Dmitrii Nikitin, notifications@github.com wrote: