Retrofit使用及分析

開始使用Retrofit

  1. 首先先聲明一個用于請求的接口
public interface GitHubService {
    @GET("users/{user}/repos")//執(zhí)行資源的地址后綴
    Call<List<User>> listRepos(@Path("user") String user);
}```
2. 創(chuàng)建一個Retrofit對象,傳入一些必要的參數(shù)

Converter.Factory factory = GsonConverterFactory.create();//使用Gson來進行數(shù)據(jù)的解析
Retrofit retrofit = new Retrofit.Builder().baseUrl("https://api.github.com/")
.addConverterFactory(factory)
.build();

3. 通過Retrofit對象通過動態(tài)代理的形式創(chuàng)建一個對象,發(fā)起一個請求。

GitHubService service = retrofit.create(GitHubService.class);
Call<List<User>> call = service.listRepos("zhaoyongchao");
call.enqueue(new Callback<List<User>>() {
@Override
public void onResponse(Call<List<User>> call, Response<List<User>> response) {
//成功后的回調(diào)
}

            @Override
            public void onFailure(Call<List<User>> call, Throwable t) {
                //失敗的回調(diào)
            }
        });
<!-- more -->
###分析具體的實現(xiàn)
- 在創(chuàng)建Retrofit對象的步驟就是一些賦值,在此只貼出build()的源碼

public Retrofit build() {
//根路徑的判斷
if (baseUrl == null) {
throw new IllegalStateException("Base URL required.");
}
//如果不傳入,則默認OKHttpClient為默認的請求工廠類
okhttp3.Call.Factory callFactory = this.callFactory;
if (callFactory == null) {
callFactory = new OkHttpClient();
}

  // 使用副本,添加默認的適配器
  List<CallAdapter.Factory> adapterFactories = new ArrayList<>(this.adapterFactories);
  
  adapterFactories.add(Platform.get().defaultCallAdapterFactory(callbackExecutor));

  // 創(chuàng)建一個用于類型轉(zhuǎn)換的副本
  List<Converter.Factory> converterFactories = new ArrayList<>(this.converterFactories);
   
  return new Retrofit(callFactory, baseUrl, converterFactories, adapterFactories,
      callbackExecutor, validateEagerly);
}

}
//區(qū)分當前運行的平臺(Android)
static class Android extends Platform {
@Override CallAdapter.Factory defaultCallAdapterFactory(Executor callbackExecutor) {
if (callbackExecutor == null) {
callbackExecutor = new MainThreadExecutor();
}
return new ExecutorCallAdapterFactory(callbackExecutor);
}

static class MainThreadExecutor implements Executor {
  //使用主線程的Looper來創(chuàng)建一個Handler,用來通信
  private final Handler handler = new Handler(Looper.getMainLooper());

  @Override public void execute(Runnable r) {
    handler.post(r);
  }
}

}

- 通過Retrofit的Create()方法來創(chuàng)建一個對象

public <T> T create(final Class<T> service) {
//判斷是否為接口
Utils.validateServiceInterface(service);
if (validateEagerly) {
eagerlyValidateMethods(service);
}
//使用Proxy來創(chuàng)建動態(tài)創(chuàng)建一個代理對象,使用返回的對象調(diào)用接口的方法都會調(diào)用匿名內(nèi)部類的invoke方法。
return (T) Proxy.newProxyInstance(service.getClassLoader(), new Class<?>[] { service },
new InvocationHandler() {
private final Platform platform = Platform.get();

      @Override public Object invoke(Object proxy, Method method, Object... args)
          throws Throwable {
        // 判斷一下聲明的類,如果是Object類,正常執(zhí)行
        if (method.getDeclaringClass() == Object.class) {
          return method.invoke(this, args);
        }
        if (platform.isDefaultMethod(method)) {
          return platform.invokeDefaultMethod(method, service, proxy, args);
        }
        return loadMethodHandler(method).invoke(args);
      }
    });

}

- 調(diào)用MethodHandler的creat()方法

static MethodHandler create(Retrofit retrofit, Method method) {
//根據(jù)方法的注解和返回類型創(chuàng)建具體的實現(xiàn)類,最終會到ExecutorCallAdapterFactory
CallAdapter<?> callAdapter = createCallAdapter(method, retrofit);
//得到泛型中的類型
Type responseType = callAdapter.responseType();
if (responseType == Response.class || responseType == okhttp3.Response.class) {
throw Utils.methodError(method, "'"
+ Types.getRawType(responseType).getName()
+ "' is not a valid response body type. Did you mean ResponseBody?");
}
//同樣創(chuàng)建具體的轉(zhuǎn)換類
Converter<ResponseBody, ?> responseConverter =
createResponseConverter(method, retrofit, responseType);
//根據(jù)請求類型和方法中的注解創(chuàng)建一個請求工廠類
RequestFactory requestFactory = RequestFactoryParser.parse(method, responseType, retrofit);
return new MethodHandler(retrofit.callFactory(), requestFactory, callAdapter,
responseConverter);
}

- createCallAdapter方法最終會調(diào)用到Retrofit中的nextCallAdapter方法

public CallAdapter<?> nextCallAdapter(CallAdapter.Factory skipPast, Type returnType,
Annotation[] annotations) {
checkNotNull(returnType, "returnType == null");
checkNotNull(annotations, "annotations == null");
//使用的是ExecutorCallAdapterFactory
int start = adapterFactories.indexOf(skipPast) + 1;
for (int i = start, count = adapterFactories.size(); i < count; i++) {
CallAdapter<?> adapter = adapterFactories.get(i).get(returnType, annotations, this);
if (adapter != null) {
return adapter;
}
}
throw new IllegalArgumentException(builder.toString());
}

- 繼續(xù)分析一下ExecutorCallAdapterFactory中的get方法

public CallAdapter<Call<?>> get(Type returnType, Annotation[] annotations, Retrofit retrofit) {
//此適配器只能處理返回類型為Call<?>
if (getRawType(returnType) != Call.class) {
return null;
}
//得到Call<T>的泛型T的類型,作為相應體的返回類型
final Type responseType = Utils.getCallResponseType(returnType);
return new CallAdapter<Call<?>>() {
@Override public Type responseType() {
return responseType;
}

  @Override public <R> Call<R> adapt(Call<R> call) {
    //創(chuàng)建一個對象進行返回
    return new ExecutorCallbackCall<>(callbackExecutor, call);
  }
};

}

- createResponseConverter得過程和上述相同不做分析。
- 根據(jù)請求類型和方法中的注解創(chuàng)建一個請求工廠類,通過parseMethodAnnotations來解析注解、parsePathParameters來解析注解的值,為工廠類相應的字段賦值。
- 調(diào)用創(chuàng)建好的MethodHandler對象的invoke方法,根據(jù)上述生成的對象創(chuàng)建OKHttpCall對象也是委派對象,把生成的對象傳入ExecutorCallAdapterFactory的adapt方法。

@Override public <R> Call<R> adapt(Call<R> call) {
return new ExecutorCallbackCall<>(callbackExecutor, call);
}

- 通過返回的Call對象的調(diào)用enqueue方法及ExecutorCallbackCall的enqueue方法

//MethodHandler中的方法
Object invoke(Object... args) {
return callAdapter.adapt(
new OkHttpCall<>(callFactory, requestFactory, args, responseConverter));
}
@Override public void enqueue(final Callback<T> callback) {
//調(diào)用及上述根據(jù)請求工廠、類型轉(zhuǎn)換工廠和請求參數(shù)創(chuàng)建的OkHttpCall對象
delegate.enqueue(new Callback<T>() {
@Override public void onResponse(final Call<T> call, final Response<T> response) {
//通過handler把回調(diào)發(fā)送到主線程
callbackExecutor.execute(new Runnable() {
@Override public void run() {
if (delegate.isCanceled()) {
// Emulate OkHttp's behavior of throwing/delivering an IOException on cancelation
callback.onFailure(call, new IOException("Canceled"));
} else {
callback.onResponse(call, response);
}
}
});
}

    @Override public void onFailure(final Call<T> call, final Throwable t) {
      callbackExecutor.execute(new Runnable() {
        @Override public void run() {
          callback.onFailure(call, t);
        }
      });
    }
  });
}
- OkHttpCall中的enqueue方法

@Override public void enqueue(final Callback<T> callback) {
okhttp3.Call call;
Throwable failure;

synchronized (this) {
  if (executed) throw new IllegalStateException("Already executed.");
  executed = true;

  call = rawCall;
  failure = creationFailure;
  if (call == null && failure == null) {
    try {
      //創(chuàng)建真是的請求
      call = rawCall = createRawCall();
    } catch (Throwable t) {
      failure = creationFailure = t;
    }
  }
}
//添加失敗回調(diào)
if (failure != null) {
  callback.onFailure(this, failure);
  return;
}

if (canceled) {
  call.cancel();
}
//真實的發(fā)起請求
call.enqueue(new okhttp3.Callback() {
  @Override public void onResponse(okhttp3.Call call, okhttp3.Response rawResponse)
      throws IOException {
    Response<T> response;
    try {
      //解析返回數(shù)據(jù)
      response = parseResponse(rawResponse);
    } catch (Throwable e) {
      callFailure(e);
      return;
    }
    callSuccess(response);
  }

  @Override public void onFailure(okhttp3.Call call, IOException e) {
    try {
      callback.onFailure(OkHttpCall.this, e);
    } catch (Throwable t) {
      t.printStackTrace();
    }
  }

  private void callFailure(Throwable e) {
    try {
      callback.onFailure(OkHttpCall.this, e);
    } catch (Throwable t) {
      t.printStackTrace();
    }
  }

  private void callSuccess(Response<T> response) {
    try {
      callback.onResponse(OkHttpCall.this, response);
    } catch (Throwable t) {
      t.printStackTrace();
    }
  }
});

}

- 到目前為止所有的注解和值已經(jīng)解析,但是沒有進行拼接??匆幌翿equestFactory的creat()方法

Request create(Object... args) throws IOException {
RequestBuilder requestBuilder =
new RequestBuilder(method, baseUrl.url(), relativeUrl, headers, contentType, hasBody,
isFormEncoded, isMultipart);

if (args != null) {
  //從注解中解析的請求類型目前使用的是RequestAction.Path
  RequestAction[] actions = requestActions;
  if (actions.length != args.length) {
    throw new IllegalArgumentException("Argument count ("
        + args.length
        + ") doesn't match action count ("
        + actions.length
        + ")");
  }
  for (int i = 0, count = args.length; i < count; i++) {
    actions[i].perform(requestBuilder, args[i]);
  }
}

return requestBuilder.build();

}
}
//RequestAction.Path類中重寫的方法
@Override void perform(RequestBuilder builder, T value) throws IOException {
if (value == null) {
throw new IllegalArgumentException(
"Path parameter "" + name + "" value must not be null.");
}
builder.addPathParam(name, valueConverter.convert(value), encoded);
}
//進行完整路徑的組合
void addPathParam(String name, String value, boolean encoded) {
if (relativeUrl == null) {
// The relative URL is cleared when the first query parameter is set.
throw new AssertionError();
}
relativeUrl = relativeUrl.replace("{" + name + "}", canonicalizeForPath(value, encoded));
}
//OKHttpClient中的 newCall轉(zhuǎn)換為一個OkHttpCall的真正請求
@Override public Call newCall(Request request) {
return new RealCall(this, request);
}

- 最終的請求在RealCall中
最后編輯于
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時請結(jié)合常識與多方信息審慎甄別。
平臺聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點,簡書系信息發(fā)布平臺,僅提供信息存儲服務。

相關(guān)閱讀更多精彩內(nèi)容

  • 適配器模式上一篇文章我們已經(jīng)分析了Retrofit解析注解封裝進ServiceMethod的流程,讀者在這里要記住...
    andcoder閱讀 772評論 0 2
  • Spring Cloud為開發(fā)人員提供了快速構(gòu)建分布式系統(tǒng)中一些常見模式的工具(例如配置管理,服務發(fā)現(xiàn),斷路器,智...
    卡卡羅2017閱讀 136,545評論 19 139
  • Retrofit 源碼解析 簡單用法 Retrofit最簡單的用法就是定義一個接口,創(chuàng)建Retrofit對象,調(diào)用...
    Kingty閱讀 949評論 3 14
  • 本文將順著構(gòu)建請求對象->構(gòu)建請求接口->發(fā)起同步/異步請求的流程,分析Retrofit是如何實現(xiàn)的。 開始之前,...
    zhuhf閱讀 1,684評論 0 10
  • 【小花涵涵】學習力四期踐行D72 2017-02-03今天節(jié)后上班第一天,一大早起床聽了彭彭的帶讀《幸福的種子》并...
    夏蘇的后花園閱讀 68評論 0 0

友情鏈接更多精彩內(nèi)容