当面时问道“Okhttp连接池是咋实现“时，app优化的内容及策略

originalRequest, this, client.connectTimeoutMillis(),

client.readTimeoutMillis(), client.writeTimeoutMillis());

try {

Response response = chain.proceed(originalRequest);

return response;

} catch (IOException e) {

} finally {

}

}

}

2.ConnectInterceptor#intercept

连接池在ConnectInterceptor中包装起来了，我们进去瞄一眼:

@Override

public Response intercept(Chain chain) throws IOException {

RealInterceptorChain realChain = (RealInterceptorChain) chain;

Request request = realChain.request();

//拿到chain的Transmitter，里面包装了RealCall、okhttpClient、connectionPool等信息

Transmitter transmitter = realChain.transmitter();

//是否不是get请求

boolean doExtensiveHealthChecks = !request.method().equals(“GET”);

Exchange exchange = transmitter.newExchange(chain, doExtensiveHealthChecks);

return realChain.proceed(request, transmitter, exchange);

}

3.Transmitter#newExchange

拿到chain的Transmitter对象，该对象是RealCall、okhttpClient、connectionPool等信息的包装类，将是否不是get请求的标识传给了transmitter的newExchange方法:

Exchange newExchange(Interceptor.Chain chain, boolean doExtensiveHealthChecks) {

//exchangeFinder是对connectionPool、connectionPool、request等信息的包装，它是在RetryAndFollowUpInterceptor拦截器中初始化出来的

ExchangeCodec codec = exchangeFinder.find(client, chain, doExtensiveHealthChecks);

Exchange result = new Exchange(this, call, eventListener, exchangeFinder, codec);

synchronized (connectionPool) {

this.exchange = result;

return result;

}

}

4.ExchangeCodec#find

该方法中将ExchangeCodec的获取交给了exchangeFinder对象，ExchangeCodec是一个接口，实现类有Http2ExchangeCodec和Http1ExchangeCodec，这两个类表示http1和http2的建立连接的类，里面实现了writeRequestHeaders和createRequestBody等方法，这两个方法是在CallServerInterceptor拦截器中使用的。exchangeFinder是对connectionPool、connectionPool、request等信息的包装，它是在RetryAndFollowUpInterceptor拦截器中初始化出来的。我们接着看exchangeFinder的find方法:

public ExchangeCodec find(

OkHttpClient client, Interceptor.Chain chain, boolean doExtensiveHealthChecks) {

int connectTimeout = chain.connectT