Kotlin + Retrofit + RxJava簡單封裝使用詳解
本文介紹了Kotlin + Retrofit + RxJava簡單封裝使用詳解,分享給大家,具體如下:
實例化Retrofit
object RetrofitUtil {
val CONNECT_TIME_OUT = 30//連接超時時長x秒
val READ_TIME_OUT = 30//讀數(shù)據(jù)超時時長x秒
val WRITE_TIME_OUT = 30//寫數(shù)據(jù)接超時時長x秒
val retrofit: Retrofit by lazy {
Log.d("RetrofitUtil", "retrofit init lazy")
Retrofit.Builder()
.baseUrl("http://gank.io/api/") //本文以GitHub API為例
.addConverterFactory(GsonConverterFactory.create())
.addCallAdapterFactory(RxJava2CallAdapterFactory.create())
.client(getOkHttpClient())
.build()
}
private fun getOkHttpClient(): OkHttpClient {
val builder = OkHttpClient.Builder()
builder.connectTimeout(CONNECT_TIME_OUT.toLong(), TimeUnit.SECONDS)
.writeTimeout(WRITE_TIME_OUT.toLong(), TimeUnit.SECONDS)
.readTimeout(READ_TIME_OUT.toLong(), TimeUnit.SECONDS)
if (BuildConfig.DEBUG) {
builder.addInterceptor(HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY))
} else {
builder.addInterceptor(HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.NONE))
}
// 設(shè)置請求頭
builder.addInterceptor { chain ->
val time = (System.currentTimeMillis() / 1000).toString() + ""
val requestBuilder = chain.request().newBuilder()
requestBuilder.addHeader("time", time)
chain.proceed(requestBuilder.build())
}
return builder.build()
}
}
返回數(shù)據(jù)封裝
class Response<T> {
var error: Boolean = false
var results: T? = null
}
demo中用了gank.io的開發(fā)api,之前一般項目的返回格式是code + message + T的格式。
api接口錯誤/異常統(tǒng)一處理類
class ApiException : Exception {
var code: Int = 0//錯誤碼
var msg: String? = null//錯誤信息
constructor(throwable: Throwable, code: Int) : super(throwable) {
this.code = code
}
constructor(code: Int, msg: String) {
this.code = code
this.msg = msg
}
}
定義ExceptionFunction處理onErrorResumeNext:
class ExceptionFunction<T> : Function<Throwable, Observable<T>> {
override fun apply(@NonNull throwable: Throwable): Observable<T> {
Log.e("ExceptionFunction", throwable.message)
return Observable.error(ExceptionEngine().handleException(throwable))
}
}
/**
* 錯誤/異常處理工具
*/
class ExceptionEngine {
val UN_KNOWN_ERROR = 1000//未知錯誤
val ANALYTIC_SERVER_DATA_ERROR = 1001//解析(服務(wù)器)數(shù)據(jù)錯誤
val CONNECT_ERROR = 1002//網(wǎng)絡(luò)連接錯誤
val TIME_OUT_ERROR = 1003//網(wǎng)絡(luò)連接超時
fun handleException(e: Throwable): ApiException {
val ex: ApiException
if (e is ApiException) { //服務(wù)器返回的錯誤
return e
} else if (e is HttpException) { //HTTP錯誤
ex = ApiException(e, e.code())
ex.msg = "網(wǎng)絡(luò)錯誤:" + ex.code
return ex
} else if (e is JsonParseException
|| e is JSONException
|| e is ParseException || e is MalformedJsonException) { //解析數(shù)據(jù)錯誤
ex = ApiException(e, ANALYTIC_SERVER_DATA_ERROR)
ex.msg = "解析錯誤"
return ex
} else if (e is ConnectException) {//連接網(wǎng)絡(luò)錯誤
ex = ApiException(e, CONNECT_ERROR)
ex.msg = "連接失敗"
return ex
} else if (e is SocketTimeoutException) {//網(wǎng)絡(luò)超時
ex = ApiException(e, TIME_OUT_ERROR)
ex.msg = "網(wǎng)絡(luò)超時"
return ex
} else { //未知錯誤
ex = ApiException(e, UN_KNOWN_ERROR)
ex.msg = e.message
return ex
}
}
}
封裝請求處理
object Rx {
/**
* Rxlifecycle綁定生命周期
*/
fun <T, E> get(observable: Observable<Response<T>>, lifecycleProvider: LifecycleProvider<E>): Observable<T> {
// 請求綁定生命周期,防止內(nèi)存泄漏,同時返回回調(diào)之后頁面已銷毀造成的空指針錯誤
if (lifecycleProvider is RxAppCompatActivity) {
val rxAppCompatActivity = lifecycleProvider as RxAppCompatActivity
observable.compose(rxAppCompatActivity.bindUntilEvent(ActivityEvent.DESTROY))
} else if (lifecycleProvider is RxFragment) {
val rxFragment = lifecycleProvider as RxFragment
observable.compose(rxFragment.bindUntilEvent(FragmentEvent.DESTROY))
}
return observable
.compose(HandleResult())
.onErrorResumeNext(ExceptionFunction())
}
/**
* 部分后臺請求
*/
fun <T> get(observable: Observable<Response<T>>): Observable<T> {
return observable
.compose(HandleResult())
.onErrorResumeNext(ExceptionFunction())
}
private class HandleResult<T> : ObservableTransformer<Response<T>, T> {
override fun apply(upstream: Observable<Response<T>>): ObservableSource<T> {
return upstream.flatMap { response -> createResult(response) }
.subscribeOn(Schedulers.io())
.unsubscribeOn(Schedulers.io())
.observeOn(AndroidSchedulers.mainThread())
}
}
private fun <T> createResult(response: Response<T>): Observable<T> {
return Observable.create({ subscriber ->
if (response.error)
throw ApiException(-1, "服務(wù)器異常") // 一般來說,自己的服務(wù)器異常會返回相應(yīng)的code和message
else
response.results?.let {
subscriber.onNext(response.results!!)
} ?: subscriber.onComplete()
})
}
}
定義HttpObserver統(tǒng)一處理返回
abstract class HttpObserver<T> : Observer<T> {
/**
* 標(biāo)記是否為特殊情況
*/
private var resultNull: Boolean = true
override fun onComplete() {
// 特殊情況:當(dāng)請求成功,但T == null時會跳過onNext,仍需當(dāng)成功處理
if (resultNull)
onSuccess(null)
}
override fun onSubscribe(d: Disposable) {
// 可在此處加上dialog
}
override fun onError(e: Throwable) {
if (e is ApiException) {
onError(e.code, e.msg)
} else {
onError(0, e.message)
}
}
override fun onNext(t: T) {
resultNull = false
onSuccess(t)
}
abstract fun onSuccess(t: T?)
/**
* 統(tǒng)一處理失敗,比如登錄失效等
*
* @param code
* @param msg
*/
open fun onError(code: Int, msg: String?) {
}
}
Api
class Result {
var _id: String? = null
var createdAt: String? = null
var desc: String? = null
var publishedAt: String? = null
var source: String? = null
var type: String? = null
var url: String = ""
var isUsed: Boolean = false
var who: String? = null
var images: List<String>? = null
/**
* 妹子小圖
*/
fun meiziSmallUrl(): String {
val meizi = url
return meizi.replace("large", "small")
}
}
interface Apiservice {
@GET("data/{type}/10/{page}")
fun getGank(@Path("type") type: String, @Path("page") page: Int): Observable<Response<List<Result>>>
}
object Api {
val apiservice: Apiservice by lazy {
Log.d("Api", "apiservice create lazy")
RetrofitUtil.retrofit.create(Apiservice::class.java)
}
}
使用
override fun loadData() {
Rx.get(Api.apiservice.getGank(getType(), mIntPage), this).subscribe(object : HttpObserver<List<Result>>() {
override fun onSuccess(t: List<Result>?) {
//getDataSuccess(t)
}
override fun onError(code: Int, msg: String?) {
super.onError(code, msg)
//getDataFailed()
}
})
}
使用了Rxlifecycle綁定生命周期來處理可能發(fā)生的內(nèi)存泄漏問題,F(xiàn)ragment跟Activity需要繼承Rx相應(yīng)的基類。
練手項目
Meizikt Gank.io Android客戶端,使用Kotlin + Retrofit2 + RxJava
以上就是本文的全部內(nèi)容,希望對大家的學(xué)習(xí)有所幫助,也希望大家多多支持腳本之家。
相關(guān)文章
Spring Boot Hazelcast Caching 使用和配置詳解
這篇文章主要介紹了Spring Boot Hazelcast Caching 使用和配置詳解,小編覺得挺不錯的,現(xiàn)在分享給大家,也給大家做個參考。一起跟隨小編過來看看吧2018-09-09
基于Zookeeper實現(xiàn)服務(wù)注冊和服務(wù)發(fā)現(xiàn)功能
無論是采用SOA還是微服務(wù)架構(gòu),都需要使用服務(wù)注冊和服務(wù)發(fā)現(xiàn)組件,本文將基于 Zookeeper 實現(xiàn)服務(wù)注冊和服務(wù)發(fā)現(xiàn)功能,如果跟我一樣有同樣的困惑,希望可以通過本文了解其他組件如何使用 Zookeeper 作為注冊中心的工作原理2023-09-09
從內(nèi)存模型中了解Java final的全部細(xì)節(jié)
關(guān)于final關(guān)鍵字,它也是我們一個經(jīng)常用的關(guān)鍵字,可以修飾在類上、或者修飾在變量、方法上,以此看來定義它的一些不可變性!像我們經(jīng)常使用的String類中,它便是final來修飾的類,并且它的字符數(shù)組也是被final所修飾的。但是一些final的一些細(xì)節(jié)你真的了解過嗎2022-03-03
IDEA Error:java: 無效的源發(fā)行版: 17錯誤
本文主要介紹了IDEA Error:java: 無效的源發(fā)行版: 17錯誤,這個錯誤是因為您的IDEA編譯器不支持Java 17版本,您需要更新您的IDEA編譯器或者將您的Java版本降級到IDEA支持的版本,本文就來詳細(xì)的介紹一下2023-08-08
關(guān)于Java實體類Serializable序列化接口的作用和必要性解析
序列化是將對象狀態(tài)轉(zhuǎn)化為可保持或者傳輸?shù)母袷竭^程,與序列化相反的是反序列化,完成序列化和反序列化,可以存儲或傳輸數(shù)據(jù),一般情況下,在定義實體類時會使用Serializable,需要的朋友可以參考下2023-05-05

