Retrofit的優點


Retrofit的優點

  1. 可以配置不同HTTP client來實現網絡請求,如okhttp、httpclient等
  2. 將接口的定義與使用分離開來,實現結構。
  3. 支持多種返回數據解析的Converter可以快速進行數據轉換。
  4. 和RxJava集成的很好
  5. 因為容易和RxJava結合使用,所以對於異步請求,同步請求也不需要做額外的工作。
  6. Retrofit是基於OKHttp

簡單使用

配置依賴

在module的build.gradle中添加

// Retrofit api "com.squareup.retrofit2:retrofit:2.3.0" api "com.squareup.retrofit2:converter-gson:2.3.0" api "com.squareup.retrofit2:adapter-rxjava2:2.3.0" // OkHttp3 api "com.squareup.okhttp3:okhttp:3.10.0" api "com.squareup.okhttp3:logging-interceptor:3.10.0" // RxJava2 api "io.reactivex.rxjava2:rxjava:2.1.9" api "io.reactivex.rxjava2:rxandroid:2.0.2" // RxLifecycle api "com.trello.rxlifecycle2:rxlifecycle:2.2.1" api "com.trello.rxlifecycle2:rxlifecycle-android:2.2.1" api "com.trello.rxlifecycle2:rxlifecycle-components:2.2.1" 
定義Retrofit單例

在Application中初始化Retrofit,因為一個Retrofit對象本身就包含一個線程池,所以我們可以初始化一個Retrofit對象,並將其做成一個全局單例對象

/** * Retrofit單例管理 * Created by Leon.W on 2019/4/28 */ public class RetrofitManager { private final String BASE_URL = "https://api.github.com"; private static RetrofitManager sInstance; private Retrofit mRetrofit; public static RetrofitManager getInstance() { if (null == sInstance) { synchronized (RetrofitManager.class) { if (null == sInstance) { sInstance = new RetrofitManager(); } } } return sInstance; } public void init() { if(mRetrofit == null) { //初始化一個OkHttpClient OkHttpClient.Builder builder = new OkHttpClient.Builder() .connectTimeout(30000, TimeUnit.MILLISECONDS) .readTimeout(30000, TimeUnit.MILLISECONDS) .writeTimeout(30000, TimeUnit.MILLISECONDS); builder.addInterceptor(new LoggingInterceptor()); OkHttpClient okHttpClient = builder.build(); //使用該OkHttpClient創建一個Retrofit對象 mRetrofit = new Retrofit.Builder() //添加Gson數據格式轉換器支持 .addConverterFactory(GsonConverterFactory.create()) //添加RxJava語言支持 .addCallAdapterFactory(RxJava2CallAdapterFactory.create()) //指定網絡請求client .client(okHttpClient) .baseUrl(BASE_URL) .build(); } } public Retrofit getRetrofit() { if(mRetrofit == null) { throw new IllegalStateException("Retrofit instance hasn't init!"); } return mRetrofit; } } 
定義ApiService
//ApiService.java public interface ApiService { @GET("/TP_S/BookList") Observable<JsonArrayBase<Book>> queryBookList(); } 
定義接口方法實現方法
//GithubAPI.java public class GithubAPI { Observable<GithubUserInfo> queryJakeWhartonInfo() { return RetrofitManager.getInstance().getRetrofit() //動態代理創建GithubAPI對象 .create(ApiService.class) .queryJakeWhartonInfo() //指定上游發送事件線程 .subscribeOn(Schedulers.computation()) //指定下游接收事件線程 .observeOn(AndroidSchedulers.mainThread()); } } 
定義返回數據實體類
public class GithubUserInfo { String login,url,name,company; int id,public_repos,followers; @Override public String toString() { return "GithubUserInfo{" + "login='" + login + '\'' + ", url='" + url + '\'' + ", name='" + name + '\'' + ", company='" + company + '\'' + ", id=" + id + ", public_repos=" + public_repos + ", followers=" + followers + '}'; } } 
調用接口
new GithubAPI().queryJakeWhartonInfo().subscribe(new Observer<GithubUserInfo>() { @Override public void onSubscribe(Disposable d) { } @Override public void onNext(GithubUserInfo githubUserInfo) { Log.d(TAG,githubUserInfo.toString()); } @Override public void onError(Throwable e) { e.printStackTrace(); Log.e(TAG,e.getMessage()); } @Override public void onComplete() { } }); >>>輸出: D/TestRetrofit: GithubUserInfo{login='JakeWharton', url='https://api.github.com/users/JakeWharton', name='Jake Wharton', company='Google, Inc.', id=66577, public_repos=102, followers=52467} 

異常處理

請求過程中的異常一般分為2種類型,一種是類似網絡異常、服務器這種環境問題;另一種比如請求參數錯誤、登錄超時、Token失效等異常。分別做如下處理

環境問題

環境異常諸如404、500、502等服務器狀態異常,或者設備本身網路異常造成的,這種時候的Exception會在onError方法中得到響應。

數據問題

數據問題諸如請求參數異常、對象為空、登錄超時等數據相關異常,這種情況Response還是會走onNext方法,只是我們需要在里面根據自定義的code,來處理各種數據異常。
下面是一個具體的基礎Observer類,在其onNext中解析
一般服務器接口返回數據會約定一個簡單的格式:

{ code:int, msg:String, data:{} //可能是對象,有可能是數組data:[] } 

對應的建議解析類,一般當接口返回先解析其code是否為成功,如果不是,那看看是否是特定的錯誤碼,把錯誤碼code和錯誤信息msg包裝成一個自定義的Exception進行處理。如果成功,則對返回結果進行進一步的解析,針對不同的接口解析成“對象”或者“數組”。

//JsonBase.java,解析code和msg public class JsonBase implements Serializable{ private static final long serialVersionUID = -6182189632617616248L; @SerializedName("msg") private String msg; private int code = -1; public int getCode() { return code; } public void setCode(int code) { this.code = code; } public String getMsg() { return msg; } public void setMsg(String msg) { this.msg = msg; } } 
//JsonArrayBase.java,解析數組類型 public class JsonArrayBase<T> extends JsonBase { @SerializedName("data") List<T> data; public List<T> getData() { return data; } public void setData(List<T> data) { this.data = data; } @Override public String toString() { StringBuilder sb = new StringBuilder(); for(int i = 0; i< data.size(); i++) { sb.append(data.get(i).toString()); } return sb.toString(); } } 
//JsonObjBase.java,解析對象類型 public class JsonObjBase<T> extends JsonBase { @SerializedName("data") T data; public T getData() { return data; } public void setData(T data) { this.data = data; } } 

基礎Observer,用於處理數據異常(即code不是SUCC的情況);網絡異常(在onError方法中進行toast提示),具體使用界面可以通過重寫onError來得到回調(比如分頁加載失敗,需要隱藏加載進度條,此時需要得到失敗回調)

//BaseObserver.java public abstract class BaseObserver<T> implements Observer<T> { private String TAG = "BaseObserver"; @Override public void onNext(T t) { if (t == null) { onError(HttpCode.ERROR_EMPTY_OBJ, getErrorMessage(HttpCode.ERROR_EMPTY_OBJ)); } else { onSuccess(t); } } /** * 外部想要處理異常(比如分頁加載失敗,需要隱藏加載中效果)時,可以重寫該方法 */ public void onError(int errorCode, String message) { } /** * 外部重寫,接受數據 * @param t */ public abstract void onSuccess(T t); /** * 不顯示服務器返回錯誤信息(部分接口返回不規范) */ public boolean isShowErrorToast() { return true; } @Override public void onError(Throwable e) { int errorCode = -1; String errMsg = ""; //自定義異常 if (e instanceof MyException) { MyException exception = (MyException) e; errorCode = exception.getErrorCode(); errMsg = exception.getMessage(); handleIybErrorCode(errorCode); if (isShowErrorToast()) { Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } } else if (e instanceof NullPointerException) { // RxJava2 發送值為null時,不執行 onNext,直接走 onError errorCode = HttpCode.ERROR_EMPTY_OBJ; errMsg = getErrorMessage(HttpCode.ERROR_EMPTY_OBJ); } else if (e instanceof SocketTimeoutException) { errorCode = HttpCode.ERROR_TIMEOUT; errMsg = getErrorMessage(HttpCode.ERROR_TIMEOUT); Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } else if (e instanceof NetworkErrorException) { errorCode = HttpCode.ERROR_NETWORK; errMsg = getErrorMessage(HttpCode.ERROR_NETWORK); Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } else if (e instanceof HttpException) { HttpException httpException = (HttpException) e; errMsg = httpException != null ? httpException.getMessage() : getErrorMessage(HttpCode.ERROR_SERVER_EXCEPTION); int httpErrorCode = httpException != null ? httpException.code() : HttpCode.ERROR_UNKNOWN; Log.d(TAG, "Http request error:" + "message=" + errMsg + " :::: " + "httpErrorCode=" + httpErrorCode); Toast.makeText(TestAPP.getInstance().getApplicationContext(), getErrorMessage(HttpCode.ERROR_SERVER_EXCEPTION),Toast.LENGTH_LONG).show(); // 統一提示服務器異常 } else { errMsg = e != null ? e.getMessage() : getErrorMessage(HttpCode.ERROR_UNKNOWN); } onError(errorCode, errMsg); } /** * 處理數據異常code * @param errorCode */ private void handleIybErrorCode(int errorCode) { if (errorCode == HttpCode.ERROR_ALREADY_REGISTER) { //已注冊處理邏輯 } else if (errorCode == HttpCode.ERROR_LOGIN_EXPIRED ) { //登錄超時處理邏輯 } } private String getErrorMessage(int errorCode) { String message = HttpCode.ERRORS.get(errorCode); if (TextUtils.isEmpty(message)) { message = HttpCode.ERRORS.get(HttpCode.ERROR_UNKNOWN); } return message; } } 
public abstract class BaseObserver<T> implements Observer<T> { private String TAG = "BaseObserver"; @Override public void onNext(T t) { if (t == null) { onError(HttpCode.ERROR_EMPTY_OBJ, getErrorMessage(HttpCode.ERROR_EMPTY_OBJ)); } else { onSuccess(t); } } /**外部想要處理異常時(比如分頁加載失敗,需要隱藏加載中效果),可以重寫該方法*/ public void onError(int errorCode, String message) { } public abstract void onSuccess(T t); /** 不顯示服務器返回錯誤信息(部分接口返回不規范) */ public boolean isShowErrorToast() { return true; } @Override public void onError(Throwable e) { int errorCode = -1; String errMsg = ""; //自定義異常 if (e instanceof MyException) { MyException exception = (MyException) e; errorCode = exception.getErrorCode(); errMsg = exception.getMessage(); handleErrorCode(errorCode); if (isShowErrorToast()) { Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } } else if (e instanceof NullPointerException) { // RxJava2 發送值為null時,不執行 onNext,直接走 onError errorCode = HttpCode.ERROR_EMPTY_OBJ; errMsg = getErrorMessage(HttpCode.ERROR_EMPTY_OBJ); } else if (e instanceof SocketTimeoutException) { errorCode = HttpCode.ERROR_TIMEOUT; errMsg = getErrorMessage(HttpCode.ERROR_TIMEOUT); Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } else if (e instanceof NetworkErrorException) { errorCode = HttpCode.ERROR_NETWORK; errMsg = getErrorMessage(HttpCode.ERROR_NETWORK); Toast.makeText(TestAPP.getInstance().getApplicationContext(), errMsg,Toast.LENGTH_LONG).show(); } else if (e instanceof HttpException) { HttpException httpException = (HttpException) e; errMsg = httpException != null ? httpException.getMessage() : getErrorMessage(HttpCode.ERROR_SERVER_EXCEPTION); int httpErrorCode = httpException != null ? httpException.code() : HttpCode.ERROR_UNKNOWN; Log.d(TAG, "Http request error:" + "message=" + errMsg + " :::: " + "httpErrorCode=" + httpErrorCode); Toast.makeText(TestAPP.getInstance().getApplicationContext(), getErrorMessage(HttpCode.ERROR_SERVER_EXCEPTION),Toast.LENGTH_LONG).show(); // 統一提示服務器異常 } else { errMsg = e != null ? e.getMessage() : getErrorMessage(HttpCode.ERROR_UNKNOWN); Toast.makeText(TestAPP.getInstance().getApplicationContext(), e.getMessage(),Toast.LENGTH_LONG).show(); // 統一提示服務器異常 } onError(errorCode, errMsg); } /** * 處理數據異常code * @param errorCode */ private void handleErrorCode(int errorCode) { if (errorCode == HttpCode.ERROR_ALREADY_REGISTER) { //已注冊處理邏輯 } else if (errorCode == HttpCode.ERROR_LOGIN_EXPIRED ) { //登錄超時處理邏輯 } } private String getErrorMessage(int errorCode) { String message = HttpCode.ERRORS.get(errorCode); if (TextUtils.isEmpty(message)) { message = HttpCode.ERRORS.get(HttpCode.ERROR_UNKNOWN); } return message; } } 
//MyException.java public class MyException extends Exception { private int mErrorCode; private String mMessage; public MyException(int errorCode, String message) { super(); mErrorCode = errorCode; mMessage = message; } public int getErrorCode() { return mErrorCode; } public void setErrorCode(int mErrorCode) { this.mErrorCode = mErrorCode; } public String getMessage() { return mMessage; } public void setMessage(String message) { this.mMessage = message; } } 
public class HttpCode { public static final int ERROR_UNKNOWN = -1; public static final int ERROR_SUCCESS = 0; // 1000~1099 自定義錯誤碼 public static final int ERROR_NETWORK = 1000; public static final int ERROR_TIMEOUT = 1001; public static final int ERROR_SERVER_EXCEPTION = 1002; public static final int ERROR_EMPTY_OBJ = 1011; public static final int ERROR_ALREADY_REGISTER = 100001; // 已經注冊過 public static final int ERROR_LOGIN_EXPIRED = 100002; // 登錄cookie超時,需要重新登錄 public static final SparseArray<String> ERRORS = new SparseArray<>(); static { ERRORS.append(ERROR_UNKNOWN, "未知錯誤"); ERRORS.append(ERROR_SUCCESS, "請求成功"); ERRORS.append(ERROR_NETWORK, "網絡錯誤"); ERRORS.append(ERROR_TIMEOUT, "連接超時"); ERRORS.append(ERROR_SERVER_EXCEPTION, "服務器異常"); ERRORS.append(ERROR_ALREADY_REGISTER, "您的手機號已經注冊過i雲保帳號"); ERRORS.append(ERROR_LOGIN_EXPIRED, "登錄超時,需要重新登錄"); ERRORS.append(ERROR_EMPTY_OBJ, "返回對象為空!"); } } 

生命周期綁定

有時我們關閉一個頁面時,希望該頁面上正在進行以及准備開始進行的請求能夠及時關閉、取消掉。以免造成內存溢出或空指針異常等問題。此時就需要將請求與頁面的生命周期相關聯。因為Retrofit和RxJava2集成,由RxJava2控制上下游的時間分發,所以處理RxJava2的生命周期問題就是處理Retrofit請求的聲明周期問題。可以看到在上面的”依賴配置“段落中導入了三個rxlifiecycle相關的依賴,其中rxliftcycle-components包含我們將要使用到的RxAppCompatActivity,而他有依賴另外兩個依賴,可以查看RxAppCompatActivity的源碼驗證:

//RxAppCompatActivity.java import com.trello.rxlifecycle2.LifecycleProvider; import com.trello.rxlifecycle2.LifecycleTransformer; //來自基礎包rxlifecycle import com.trello.rxlifecycle2.RxLifecycle; //來自android包rxlifecycle-android import com.trello.rxlifecycle2.android.ActivityEvent; //來自android包rxlifecycle-android import com.trello.rxlifecycle2.android.RxLifecycleAndroid; import io.reactivex.Observable; import io.reactivex.subjects.BehaviorSubject; public abstract class RxAppCompatActivity extends AppCompatActivity implements LifecycleProvider<ActivityEvent> { ...... } 

下面開始聲明周期相關的Demo,演示一下未綁定頁面生命周期導致內存溢出的問題,假設有一個Activity中有一個operator每隔1秒發送一個事件:

public class TestMemLeakActivity extends Activity { private String TAG = "TestMemLeak"; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.rx_act_test_leak); Observable.interval(1000l, TimeUnit.MILLISECONDS) .subscribeOn(Schedulers.computation()) .observeOn(AndroidSchedulers.mainThread()) .subscribe(new Observer<Long>() { @Override public void onSubscribe(Disposable d) { } @Override public void onNext(Long aLong) { Log.d(TAG,aLong + ""); } @Override public void onError(Throwable e) { Log.d(TAG,e.getMessage()); } @Override public void onComplete() { Log.d(TAG,"onComplete"); } }); } @Override protected void onDestroy() { super.onDestroy(); Log.d(TAG,"onDestory------"); } } >>>輸出: 04-29 19:38:00.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 0 04-29 19:38:01.101 18964-18964/com.ebm.rxjava D/TestMemLeak: 1 04-29 19:38:02.101 18964-18964/com.ebm.rxjava D/TestMemLeak: 2 04-29 19:38:03.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 3 04-29 19:38:04.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 4 04-29 19:38:05.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 5 04-29 19:38:05.110 18964-18964/com.ebm.rxjava D/TestMemLeak: onDestory------ 04-29 19:38:06.105 18964-18964/com.ebm.rxjava D/TestMemLeak: 6 04-29 19:38:07.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 7 04-29 19:38:08.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 8 04-29 19:38:09.102 18964-18964/com.ebm.rxjava D/TestMemLeak: 9 

從Log可以看出,TestMemLeakActivity關閉調用onDestory()之后,事件沒有隨着界面關閉而停止發送,這樣會導致Activity無法回收,進而導致內存泄露。下面使用RxAppCompatActivity進行將RxJava綁定到Activity的聲明周期。

//1.繼承自RxAppCompatActivity public class TestMemLeakActivity extends RxAppCompatActivity { private String TAG = "TestMemLeak"; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.rx_act_test_leak); Observable.interval(1000l, TimeUnit.MILLISECONDS) .subscribeOn(Schedulers.computation()) .observeOn(AndroidSchedulers.mainThread()) //2.綁定聲明周期 .compose(this.<Long>bindToLifecycle()) .subscribe(new Observer<Long>() { @Override public void onSubscribe(Disposable d) { } @Override public void onNext(Long aLong) { Log.d(TAG,aLong + ""); } @Override public void onError(Throwable e) { Log.d(TAG,e.getMessage()); } @Override public void onComplete() { Log.d(TAG,"onComplete"); } }); } @Override protected void onDestroy() { super.onDestroy(); Log.d(TAG,"onDestory------"); } } >>>輸出: 04-29 19:41:41.254 20080-20080/com.ebm.rxjava D/TestMemLeak: 0 04-29 19:41:42.254 20080-20080/com.ebm.rxjava D/TestMemLeak: 1 04-29 19:41:43.254 20080-20080/com.ebm.rxjava D/TestMemLeak: 2 04-29 19:41:44.253 20080-20080/com.ebm.rxjava D/TestMemLeak: 3 04-29 19:41:44.762 20080-20080/com.ebm.rxjava D/TestMemLeak: onComplete 04-29 19:41:44.762 20080-20080/com.ebm.rxjava D/TestMemLeak: onDestory------ 

從上面的Log可以看出,界面關閉之前先發送了onComplete事件,關閉了事件流的發送。

 


免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM