1.RxJava概念及原理
RxJava –
Reactive Extensions for the JVM – a library for composing asynchronous
and event-based programs using observable sequences for the Java VM.
為JVM設計使用可觀測序列組成異步基于事件的程序庫,核心使用觀察者模式,以鏈式函數調用形式展示
2.x相對于1.x的改動
- 操作符基本沒有變化,Action命名變化
Rx1.0-----------Rx2.0
Action1--------Action
Action1--------Consumer
Action2--------BiConsumer
后面的Action都去掉了,只保留了ActionN
Function和RxJava1.0相比,他們都增加了throws Exception,也就是說,在這些方法做某些操作就不需要try-catch。
Flowable.just("file.txt").map(name->Files.readLines(name)).subscribe(lines->System.out.println(lines.size()),Throwable::printStackTrace);
- 把支持背壓的Observable單獨抽出來到類Flowable
- Scheduler中移除了Schedulers.immediate()這個線程環境,io.reactivex.Scheduler這個抽象 類支持直接調度自定義線程任務
網友指出的rxjava1到2升級踩坑實戰 ,不過官方提供了1.x到2.x的遷移庫(RxJava2Interop )
2.操作符、背壓、Scheduler、Hook以及結合Lambda
2.1 操作符
2.1.1 subscribeOn與ObserveOn
此處以subscribeOn為例
2.1.2 map、flatMap、switchMap、concatMap
此處以flatMap為例
涉及到的類圖
flatMap:無法保證事件隊列U是按序排列
試例:
private void testFlatMap(){
Log.d(TAG, "testFlatMap start");
Observable.just("A", "B", "C", "D", "E").flatMap(new Function<String, Observable<String>>() {
@Override
public Observable<String> apply(String s) throws Exception {
Log.d(TAG,"testFlatMap apply "+s);
return Observable.just(s + "1",s + "2").subscribeOn(Schedulers.newThread());
}
}).observeOn(AndroidSchedulers.mainThread()).subscribe(new Observer<String>() {
@Override
public void onSubscribe(Disposable d) {
}
@Override
public void onComplete() {
Log.d(TAG,"testFlatMap ------>onCompleted()");
}
@Override
public void onError(Throwable e) {
Log.d(TAG,"testFlatMap ------>onError()" + e);
}
@Override
public void onNext(String s) {
Log.d(TAG,"testFlatMap ------>onNext:" + s);
}
}/*s -> {Log.d(TAG,"testFlatMap ------>accept:" + s);int i = 1 / 0;} ,e -> Log.d(TAG,"testFlatMap ------>onError()" + e)*/);
Log.d(TAG, "testFlatMap end");
}
運行結果:
03-22 19:48:32.188 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap start
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap apply A
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap apply B
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap apply C
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap apply D
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap apply E
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap end
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:A1
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:A2
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:B1
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:B2
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:D1
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:D2
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:E1
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:E2
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:C1
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onNext:C2
03-22 19:48:32.198 2092-2092/com.example.administrator.rxjavademo D/MainActivity: testFlatMap ------>onCompleted()
concatMap:可以保證按序
草圖(非標準類圖、非標準時序圖,orz...)如下
試例:
同上 換成concatMap
運行結果:
03-22 19:55:31.658 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap start
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap apply A
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap end
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:A1
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:A2
03-22 19:55:31.668 10937-15859/com.example.administrator.rxjavademo D/MainActivity: testConcatMap apply B
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:B1
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:B2
03-22 19:55:31.668 10937-15860/com.example.administrator.rxjavademo D/MainActivity: testConcatMap apply C
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:C1
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:C2
03-22 19:55:31.668 10937-15861/com.example.administrator.rxjavademo D/MainActivity: testConcatMap apply D
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:D1
03-22 19:55:31.668 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:D2
03-22 19:55:31.668 10937-15862/com.example.administrator.rxjavademo D/MainActivity: testConcatMap apply E
03-22 19:55:31.678 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:E1
03-22 19:55:31.678 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onNext:E2
03-22 19:55:31.678 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testConcatMap ------>onCompleted()
switchMap:舊的中間Observable<U>產生的事件序列沒有發送完畢,在下一個中間的Observable開始發送后則停止對原事件序列訂閱下發
草圖(非標準類圖、非標準時序圖,orz...)如下
試例:
同上 換成switchMap
運行結果:
03-22 19:53:55.538 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap start
03-22 19:53:55.558 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap apply A
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap apply B
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap apply C
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap apply D
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap apply E
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap end
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap ------>onNext:E1
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap ------>onNext:E2
03-22 19:53:55.568 10937-10937/com.example.administrator.rxjavademo D/MainActivity: testSwitchMap ------>onCompleted()
2.2背壓
場景:
當生產者生產事件過慢,消費者消費事件過快,消費者阻塞等待生產者,沒有問題
當生產者生產事件過快,而消費者消費事件過慢的情況下,需要額外的緩存開銷去容納生產過剩的事件,而背壓提供了異步場景下對生產者流速控制的策略
RxJava2.x中把支持背壓的函數分離到Flowable類,Observable類中不支持背壓
方式:
1.React pull mode
標準的RxJava是push mode,觀察者Subscriber發起訂閱后,事件流就從被觀察者Flowable中生產并push過來,如何將push mode切換到pull mode的方法是Subscription的request方法
上圖為網上copy的,下游文字寫錯,糾正下
//Flowable需要加主動request的,背壓策略
private void testFlowable(){
Log.d(TAG,"testFlowable start");
// Flowable.range(1, 10)
// .subscribeOn(Schedulers.computation())
// .map(v -> v * v)
// .subscribe(i -> Log.d(TAG,"range onNext "+i));
List<Integer> list = new ArrayList<Integer>();
for(int i=0 ; i<10; i++){
list.add(i);
}
Flowable.fromIterable(list)
.subscribeOn(Schedulers.computation())
.subscribe(/*i -> Log.d(TAG,"fromIterable onNext "+i)*/
new Subscriber<Integer>() {
Subscription subcription;
@Override
public void onSubscribe(Subscription s) {
Log.d(TAG,"fromIterable onSubscribe "+s);
subcription = s;
subcription.request(1);//默認實現Long.MAX_VALUE
}
@Override
public void onNext(Integer integer) {
Log.d(TAG,"fromIterable onNext "+integer);
subcription.request(1);
}
@Override
public void onError(Throwable t) {
Log.d(TAG,"fromIterable onError "+t);
}
@Override
public void onComplete() {
Log.d(TAG,"fromIterable onComplete");
}
});
Log.d(TAG,"testFlowable end");
}
輸出結果:
03-23 16:57:19.718 8740-8740/com.example.administrator.rxjavademo D/MainActivity: testFlowable start
03-23 16:57:19.758 8740-8740/com.example.administrator.rxjavademo D/MainActivity: fromIterable onSubscribe null
03-23 16:57:19.758 8740-8740/com.example.administrator.rxjavademo D/MainActivity: testFlowable end
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 0
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 1
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 2
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 3
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 4
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 5
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 6
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 7
03-23 16:57:19.758 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 8
03-23 16:57:19.768 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onNext 9
03-23 16:57:19.768 8740-9904/com.example.administrator.rxjavademo D/MainActivity: fromIterable onComplete
2.丟棄sample、緩沖buffer window
3.onBackpresureBuffer、onBackPressureDrop
此處牽涉到兩個概念
Hot Observable跟Cold Observable
Hot Observable指的是被觀察者創建即開始生產事件發送,不等有觀察者訂閱才發送,如鼠標事件、股票價格 Observable.pulish()可以把cold observable轉換為hot observable
Cold Observable指的是一般的被觀察者等有觀察者訂閱才開始生產事件發送,interval range函數創建的都屬于該類
總結:
背壓只適用于異步場景,并不是說同步場景也需要用背壓策略去流速控制
針對flowable事件發布速率過快的場景肯定需要加上request做背壓
2.3 Scheduler
2.4 Hook
2.5 Lambada
3.android項目應用舉例(結合retrofit)
3.1 先添加rxAndroid依賴(默認會自動引入對應的rxJava包)
dependencies {
compile"com.squareup.retrofit2:retrofit:$parent.ext.retrofitVersion"
compile"com.squareup.retrofit2:adapter-rxjava2:$parent.ext.retrofitVersion"
compile"com.squareup.retrofit2:converter-gson:$parent.ext.retrofitVersion"
compile"com.squareup.retrofit2:converter-scalars:$parent.ext.retrofitVersion"
compile"com.squareup.okhttp3:logging-interceptor:$parent.ext.okhttpVersion"
compile"io.reactivex.rxjava2:rxandroid:$parent.ext.rxAndroidVersion"
}
3.2 retrofit添加callAdapter適配業務接口方法返回類型為Observable
業務接口方法形如
@GET("{headUrl}")
Observable<String> getNewstockCount(
@Path(value ="headUrl",encoded =true) String url,
@QueryMapMap params);
此處Observable<String>一般使用會替換成Observable<T> T指的是接受通用返回body的bean類
rerotfit構造如下
public static Retrofit getRetrofitInstance(){
OkHttpClient okHttpClient = new OkHttpClient.Builder()
.addInterceptor(new HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY))
.connectTimeout(DEFAULT_TIMEOUT, TimeUnit.SECONDS)
.writeTimeout(DEFAULT_TIMEOUT, TimeUnit.SECONDS)
.readTimeout(DEFAULT_TIMEOUT, TimeUnit.SECONDS).build();
return new Retrofit.Builder().baseUrl("XXX")
.addCallAdapterFactory(RxJava2CallAdapterFactory.createAsync())
.addConverterFactory(ScalarsConverterFactory.create()).client(okHttpClient).build();
}
這里加粗的String一般實際運用根據業務需要指定接受相應body的bean類型
3.3直接使用返回的Observable進行subscribe做相應的鏈式處理
private void testRetrofit(){
Log.d(TAG, "testRetrofit start");
//結合retrofit使用
NetworkApi networkApi = RetrofitFactory.getRetrofitInstance().create(NetworkApi.class);
networkApi.getNewstockCount("XXXX",new HashMap<String,Object>()).subscribe(new Observer<String>(){
@Override
public void onSubscribe(Disposable d) {
}
@Override
public void onComplete() {
Log.d(TAG,"onCompleted");
}
@Override
public void onError(Throwable e) {
Log.d(TAG,"onError="+e.getLocalizedMessage());
}
@Override
public void onNext(String stringResponse) {
Log.d(TAG,"onNext="+stringResponse);
}
});
Log.d(TAG, "testRetrofit end");
}
4.相關開源庫(RxBus、RxBinding、frodo、RxLifecycle)
5.優缺點
優點:
1.鏈式調用讓用例流程清晰明了,某種程度上來說也是解耦,不再需要Handler 、new Thread
2.強大的數據變換功能以及線程切換,實際運用項目的時候可以插拔自己項目的線程池策略
缺點:
1.學習成本比較高,需要理解各種操作符,初期使用可能會有函數比較冗長的即視感
2.rxjava庫升級帶來的項目替換成本