网络编程-Retrofit库源码分析(1)

Converter获取

分为请求和结果两种；converterFactories中每个工厂，根据注解，如果生产Converter类，则返回

public Converter<T, RequestBody> requestBodyConverter(

Type type, Annotation[] parameterAnnotations, Annotation[] methodAnnotations) {

return nextRequestBodyConverter(null, type, parameterAnnotations, methodAnnotations);

}

public Converter<T, RequestBody> nextRequestBodyConverter(

@Nullable Converter.Factory skipPast,

Type type,

Annotation[] parameterAnnotations,

Annotation[] methodAnnotations) {

Objects.requireNonNull(type, “type == null”);

Objects.requireNonNull(parameterAnnotations, “parameterAnnotations == null”);

Objects.requireNonNull(methodAnnotations, “methodAnnotations == null”);

int start = converterFactories.indexOf(skipPast) + 1;

for (int i = start, count = converterFactories.size(); i < count; i++) {

Converter.Factory factory = converterFactories.get(i);

Converter<?, RequestBody> converter =

factory.requestBodyConverter(type, parameterAnnotations, methodAnnotations, this);

if (converter != null) {

//noinspection unchecked

return (Converter<T, RequestBody>) converter;

}

}

。。。

}

public Converter<ResponseBody, T> responseBodyConverter(Type type, Annotation[] annotations) {

return nextResponseBodyConverter(null, type, annotations);

}

public Converter<ResponseBody, T> nextResponseBodyConverter(

@Nullable Converter.Factory skipPast, Type type, Annotation[] annotations) {

Objects.requireNonNull(type, “type == null”);

Objects.requireNonNull(annotations, “annotations == null”);

int start = converterFactories.indexOf(skipPast) + 1;

for (int i = start, count = converterFactories.size(); i < count; i++) {

Converter<ResponseBody, ?> converter =

converterFactories.get(i).responseBodyConverter(type, annotations, this);

if (converter != null) {

//noinspection unchecked

return (Converter<ResponseBody, T>) converter;

}

}

。。。

}

3.1.5 回调线程适配

主要处理okhttp请求结果回调执行线程问题，同样可以添加自定义，也有默认处理

public Builder addCallAdapterFactory(CallAdapter.Factory factory) {

callAdapterFactories.add(Objects.requireNonNull(factory, “factory == null”));

return this;

}

---

List<CallAdapter.Factory> callAdapterFactories = new ArrayList<>(this.callAdapterFactories);

callAdapterFactories.addAll(platform.defaultCallAdapterFactories(callbackExecutor));

默认有两个DefaultCallAdapterFactory， 如果android sdk >=24,还会有CompletableFutureCallAdapterFactory；

CallAdapter获取

callAdapterFactories中每个工厂类，通过注解获取可以处理的适配器，如果不为空则找到；

public CallAdapter<?, ?> callAdapter(Type returnType, Annotation[] annotations) {

return nextCallAdapter(null, returnType, annotations);

}

public CallAdapter<?, ?> nextCallAdapter(

@Nullable CallAdapter.Factory skipPast, Type returnType, Annotation[] annotations) {

Objects.requireNonNull(returnType, “returnType == null”);

Objects.requireNonNull(annotations, “annotations == null”);

int start = callAdapterFactories.indexOf(skipPast) + 1;

for (int i = start, count = callAdapterFactories.size(); i < count; i++) {

CallAdapter<?, ?> adapter = callAdapterFactories.get(i).get(returnType, annotations, this);

if (adapter != null) {

return adapter;

}

}

。。。

}

3.2 执行过程

介绍下异步过程，通过过程在请求方法上存在区别，流程处理基本一致

3.2.1 动态代理

public T create(final Class service) {

validateServiceInterface(service);

return (T)

Proxy.newProxyInstance(

service.getClassLoader(),

new Class<?>[] {service},

new InvocationHandler() {

private final Platform platform = Platform.get();

private final Object[] emptyArgs = new Object[0];

@Override

public @Nullable Object invoke(Object proxy, Method method, @Nullable Object[] args)

throws Throwable {

if (method.getDeclaringClass() == Object.class) {

return method.invoke(this, args);

}

args = args != null ? args : emptyArgs;

return platform.isDefaultMethod(method)

? platform.invokeDefaultMethod(method, service, proxy, args)

loadServiceMethod(method).invoke(args);

}

});

}

分两种情况

1. 接口有默认实现，使用Lookup、MethodHandles的反射技术，来实现方法调用；这种反射技术需要知道调用类信息，方法、字段信息，才可以反射调用； 没有用过这种思路

2. 通过ServiceMethod.invoke来构造返回方法结果，这个是Okhttp中可请求的参数结果

3.2.2 ServiceMethod 构造请求

其抽象实现类HttpServiceMethod， 具体实现类CallAdapted，SuspendForResponse，SuspendForBody；抽象方法为

protected abstract @Nullable ReturnT adapt(Call call, Object[] args);

主要是再invoke方法中调用；其它方法实现了CallAdapter的获取，respondBody 的Converter的获取，也是通过Retrofit代理获取的

final @Nullable ReturnT invoke(Object[] args) {

Call call = new OkHttpCall<>(requestFactory, args, callFactory, responseConverter);

return adapt(call, args);

}

serviceMethodCache用来缓存Method信息、方法注解信息、方法参数注解信息；parseAnnotations方法就是来解析注解信息的

ServiceMethod<?> loadServiceMethod(Method method) {

ServiceMethod<?> result = serviceMethodCache.get(method);

if (result != null) return result;

synchronized (serviceMethodCache) {

result = serviceMethodCache.get(method);

if (result == null) {

result = ServiceMethod.parseAnnotations(this, method);

serviceMethodCache.put(method, result);

}

}

return result;

}

3.2.3 注解解析过程

请求信息收集

RequestFactory的parseAnnotations方法进行收集；方法注解直接收集并解析；参数注解通过ParameterHandler子类+参数值来实现解析，create方法即为完成参数注解解析过程

callAdapter、Converter<ResponseBody, ResponseT>收集

HttpServiceMethod类中HttpServiceMethod方法来实现

3.2.4 开始异步请求

invoke方法执行开始请求，其内部由HttpServiceMethod 子类中通过adapt方法，这个方法进而调用callAdapter方法

final @Nullable ReturnT invoke(Object[] args) {

Call call = new OkHttpCall<>(requestFactory, args, callFactory, responseConverter);

return adapt(call, args);

}

---

callAdapter.adapt(call)

callAdapter其实是对OkhttpCall回调方法进行了包装；

1. 不进行任何包装

2. 包装为DefaultCallAdapterFactory.ExecutorCallbackCall，如果提供了线程池，则回调在线程池中执行

3. 包装为CompletableFutureCallAdapterFactory.ResponseCallback，异步执行

3.3 异步结果处理

主要在OkHttpCall中进行

public void enqueue(final Callback callback) {

Objects.requireNonNull(callback, “callback == null”);

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 {

call = rawCall = createRawCall();

} catch (Throwable t) {

throwIfFatal(t);

failure = creationFailure = t;

}

}

}

if (failure != null) {

callback.onFailure(this, failure);

return;

}

if (canceled) {

call.cancel();

}

call.enqueue(

new okhttp3.Callback() {

@Override

public void onResponse(okhttp3.Call call, okhttp3.Response rawResponse) {

Response response;

try {

response = parseResponse(rawResponse);

} catch (Throwable e) {

throwIfFatal(e);

callFailure(e);

return;

}

try {

callback.onResponse(OkHttpCall.this, response);

} catch (Throwable t) {

throwIfFatal(t);

t.printStackTrace(); // TODO this is not great

}

}

@Override

public void onFailure(okhttp3.Call call, IOException e) {

callFailure(e);

}

private void callFailure(Throwable e) {

最后

在这里小编整理了一份Android大厂常见面试题，和一些Android架构视频解析，都已整理成文档，全部都已打包好了，希望能够对大家有所帮助，在面试中能顺利通过。

喜欢本文的话，不妨顺手给我点个小赞、评论区留言或者转发支持一下呗

《Android学习笔记总结+移动架构视频+大厂面试真题+项目实战源码》，点击传送门，即可获取！
t) {

throwIfFatal(t);

t.printStackTrace(); // TODO this is not great

}

}

@Override

public void onFailure(okhttp3.Call call, IOException e) {

callFailure(e);

}

private void callFailure(Throwable e) {

最后

在这里小编整理了一份Android大厂常见面试题，和一些Android架构视频解析，都已整理成文档，全部都已打包好了，希望能够对大家有所帮助，在面试中能顺利通过。

[外链图片转存中…(img-1rMDF2pn-1715127469195)]

[外链图片转存中…(img-t3uXRNXd-1715127469197)]

喜欢本文的话，不妨顺手给我点个小赞、评论区留言或者转发支持一下呗

《Android学习笔记总结+移动架构视频+大厂面试真题+项目实战源码》，点击传送门，即可获取！