上一篇文章当中，我介绍了CacheDispatcher和缓存类Cache是怎么根据request从缓存中获取到数据的，接下来这篇文章，将会介绍网络数据的获取。
对比缓存的获取，其实我们也有两个类，一个是NetworkDispatcher，一个是Network，前者是线程，后者是对抽象的网络的实体化。
这样的设计方式也是值得我们学习的，因为Network会负责处理网络请求过程中遇到的各种问题，这些问题在设计上来说，不应该和让NetworkDispatcher关心。NetworkDispatcher只是负责处理Network给出的Response既可以了。
下面我们先来看NetworkDispatcher
/**
* Creates a new network dispatcher thread. You must call {@link #start()}
* in order to begin processing.
*
* @param queue Queue of incoming requests for triage
* @param network Network interface to use for performing requests
* @param cache Cache interface to use for writing responses to cache
* @param delivery Delivery interface to use for posting responses
*/
public NetworkDispatcher(BlockingQueue<Request<?>> queue,
Network network, Cache cache,
ResponseDelivery delivery) {
mQueue = queue;//请求队列
mNetwork = network;//网络
mCache = cache;//缓存
mDelivery = delivery;//分发器
}请求队列mQueue是为了从中取出request,network是用于获取网络数据，cache是在获取到网络数据以后，可以把这些数据加入缓存。
至于分发器，就是为了讲response分发给对应的request。
接下来看run()方法
@Override
public void run() {
Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);//设置线程优先级
while (true) {
long startTimeMs = SystemClock.elapsedRealtime();
Request<?> request;
try {
// Take a request from the queue.
request = mQueue.take();
} catch (InterruptedException e) {
// We may have been interrupted because it was time to quit.
if (mQuit) {
return;
}
continue;
}
try {
request.addMarker("network-queue-take");
// If the request was cancelled already, do not perform the
// network request.
if (request.isCanceled()) {
request.finish("network-discard-cancelled");
continue;
}
addTrafficStatsTag(request);//统计流量
// Perform the network request. 从网络解析请求,获得响应
NetworkResponse networkResponse = mNetwork.performRequest(request);
request.addMarker("network-http-complete");
// If the server returned 304 AND we delivered a response already,
// we're done -- don't deliver a second identical response.
if (networkResponse.notModified && request.hasHadResponseDelivered()) {
request.finish("not-modified");
continue;
}
// Parse the response here on the worker thread. 解析网络响应到本地
Response<?> response = request.parseNetworkResponse(networkResponse);
request.addMarker("network-parse-complete");
// Write to cache if applicable.
// TODO: Only update cache metadata instead of entire record for 304s.
if (request.shouldCache() && response.cacheEntry != null) {
mCache.put(request.getCacheKey(), response.cacheEntry);
request.addMarker("network-cache-written");
}
// Post the response back.
request.markDelivered();
mDelivery.postResponse(request, response);
} catch (VolleyError volleyError) {
volleyError.setNetworkTimeMs(SystemClock.elapsedRealtime() - startTimeMs);
parseAndDeliverNetworkError(request, volleyError);
} catch (Exception e) {
VolleyLog.e(e, "Unhandled exception %s", e.toString());
VolleyError volleyError = new VolleyError(e);
volleyError.setNetworkTimeMs(SystemClock.elapsedRealtime() - startTimeMs);
mDelivery.postError(request, volleyError);
}
}
}1，从请求队列中取出请求request，交给network处理,network返回响应NetworkResponse。NetworkResponse是我们自己构造的类，用于代表网络响应。
2，判断NetworkResponse中的http状态码，如果304，表示资源没有被修改(说明我们之前已经请求过这个资源了)，结束即可
3，否则，将NetworkResponse包装成本地Response,如果request要求缓存，则cache缓存
4，最后分发器将response分发给reuqest进行解析
上面的过程，可能大家会有一些疑惑。
首先是NetworkResponse类，其实这个类就代表一个网络响应，但是由于我们要面向抽象编程，就将这个NetworkResponse包装成我们自己定义的Response<T>类（这个类以后会介绍）。
对比缓存的那章，我们可以看到，Cache获取的其实是一个Entry实例，最后也是要包装成Response，再交给分发器分发。
这种思想有点类似适配器模式，是为了解决接口不统一的问题，对应request来说，针对的只是reponse，至于response的细节，reuqest也不想关心，只要它提供规定的接口就可以了。所以说response更像是一层包装，里面的细节可能很复杂很混乱，但是只要最后对外的接口是统一的既可以了。
值得我们注意的，还有这段代码对错误的处理。
还有我们可以看到，如果在数据请求过程中出错，所有的错误，都会被包装成VolleyError类，然后由分发器交给request处理。这里的思想和上面所说的一模一样，我就不再赘述了。
另外一个疑惑就是network具体是怎么从网络中获取数据的呢？这里就要求我们去了解这个类的源码了。
/**
* An interface for performing requests.
* 执行请求的网络,接口
*/
public interface Network {
/**
* Performs the specified request.
* @param request Request to process
* @return A {@link NetworkResponse} with data and caching metadata; will never be null
* @throws VolleyError on errors
* 执行对应的请求,返回响应
*/
public NetworkResponse performRequest(Request<?> request) throws VolleyError;
}
首先是一些简单的属性
/**
* A network performing Volley requests over an {@link HttpStack}.
* 一个在httpstack上执行volley请求的网络
*/
public class BasicNetwork implements Network {
/**
* 是否debug
*/
protected static final boolean DEBUG = VolleyLog.DEBUG;
/**
* 判断请求时间是否过长的标准
*/
private static int SLOW_REQUEST_THRESHOLD_MS = 3000;
/**
* 默认缓冲池数
*/
private static int DEFAULT_POOL_SIZE = 4096;
/**
* http执行栈
*/
protected final HttpStack mHttpStack;
/**
* 缓冲数组池
*/
protected final ByteArrayPool mPool;我先来说明一下这个两个属性的作用吧。
HttpStack mHttpStack是实际的网络请求类，有的朋友可能会吐槽，怎么HttpStack是网络请求类，那么network又是干什么的呢？网络请求写在network里面不就好了吗？为什么把整个过程弄得更加复杂。
这是很好的问题。首先HttpStack的具体实现其实有两个版本(也就是说有两个子类，一个是用httpclient,一个是用urlConnetion)，OK，为了我们可以选择性地使用这两种请求方式，设计HttpStack这个类是合理的。因为如果将两种方式都写到network里面，耦合就过重了。
另外，network作为网络的实体，处理的更多应该是网络问题，例如网络连接错误，地址重定向，401身份验证错误等；而HttpStack则不应该关心它们。
从这个设计的角度来看，分离出HttpStack也是合理的。
再看ByteArrayPool，这个类总的来说就是为io流读取和写入的时候提供缓冲区的。在java编程中，我在用io流写入的时候，经常会先申请一个byte[]来作为缓冲区，这个类的设计目的是为了减少缓存区的重复申请。
接下来，我们直接看BasicNetwork的performRequest()方法，看它是如何利用HttpStack来获取数据，以及如何处理和网络有关的错误的。
@Override
/**
* 执行对应的请求,返回响应
*/
public NetworkResponse performRequest(Request<?> request) throws VolleyError {
long requestStart = SystemClock.elapsedRealtime();//请求开始执行时间
while (true) {
HttpResponse httpResponse = null;
byte[] responseContents = null;//响应内容
Map<String, String> responseHeaders = Collections.emptyMap();
try {
// Gather headers.收集http头
Map<String, String> headers = new HashMap<String, String>();
addCacheHeaders(headers, request.getCacheEntry());//添加缓存中的头
httpResponse = mHttpStack.performRequest(request, headers);//执行请求，获取响应
StatusLine statusLine = httpResponse.getStatusLine();//http响应状态
int statusCode = statusLine.getStatusCode();//http标准回应信息
responseHeaders = convertHeaders(httpResponse.getAllHeaders());//将响应头数组转换成map形式s
// Handle cache validation.
if (statusCode == HttpStatus.SC_NOT_MODIFIED) {//304,自从上次请求后，请求的网页未修改过
Entry entry = request.getCacheEntry();
if (entry == null) {
return new NetworkResponse(HttpStatus.SC_NOT_MODIFIED, null,
responseHeaders, true,
SystemClock.elapsedRealtime() - requestStart);
}
// A HTTP 304 response does not have all header fields. We
// have to use the header fields from the cache entry plus
// the new ones from the response.
// http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5
entry.responseHeaders.putAll(responseHeaders);
return new NetworkResponse(HttpStatus.SC_NOT_MODIFIED, entry.data,
entry.responseHeaders, true,
SystemClock.elapsedRealtime() - requestStart);
}
// Handle moved resources 网络资源被移动(301,302)，修改重定向地址
if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY || statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {
String newUrl = responseHeaders.get("Location");
request.setRedirectUrl(newUrl);
}
// Some responses such as 204s do not have content. We must check.
if (httpResponse.getEntity() != null) {//返回响应主体
responseContents = entityToBytes(httpResponse.getEntity());//将主体转换byte[]形式
} else {//没有返回内容
// Add 0 byte response as a way of honestly representing a
// no-content request.
responseContents = new byte[0];
}
// if the request is slow, log it.如果请求时间过长，记录之
long requestLifetime = SystemClock.elapsedRealtime() - requestStart;
logSlowRequests(requestLifetime, request, responseContents, statusLine);
if (statusCode < 200 || statusCode > 299) {//网络错误
throw new IOException();
}
return new NetworkResponse(statusCode, responseContents, responseHeaders, false,
SystemClock.elapsedRealtime() - requestStart);
} catch (SocketTimeoutException e) {
attemptRetryOnException("socket", request, new TimeoutError());
} catch (ConnectTimeoutException e) {
attemptRetryOnException("connection", request, new TimeoutError());
} catch (MalformedURLException e) {
throw new RuntimeException("Bad URL " + request.getUrl(), e);
} catch (IOException e) {
int statusCode = 0;
NetworkResponse networkResponse = null;
if (httpResponse != null) {//没有响应，说明网络连接有问题
statusCode = httpResponse.getStatusLine().getStatusCode();
} else {
throw new NoConnectionError(e);
}
if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY ||
statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {//302,301
VolleyLog.e("Request at %s has been redirected to %s", request.getOriginUrl(), request.getUrl());
} else {
VolleyLog.e("Unexpected response code %d for %s", statusCode, request.getUrl());
}
if (responseContents != null) {//有响应内容
networkResponse = new NetworkResponse(statusCode, responseContents,
responseHeaders, false, SystemClock.elapsedRealtime() - requestStart);
if (statusCode == HttpStatus.SC_UNAUTHORIZED ||
statusCode == HttpStatus.SC_FORBIDDEN) {//401,请求要求身份验证;403,服务器拒绝请求
attemptRetryOnException("auth",//尝试重新请求
request, new AuthFailureError(networkResponse));
} else if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY ||
statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {//302,301
attemptRetryOnException("redirect",//尝试重定向请求
request, new AuthFailureError(networkResponse));
} else {
// TODO: Only throw ServerError for 5xx status codes.
throw new ServerError(networkResponse);//抛出服务器异常
}
} else {
throw new NetworkError(networkResponse);
}
}
}
}httpResponse = mHttpStack.performRequest(request, headers);//执行请求，获取响应首先是处理304（Not Modified）
// Handle cache validation.
if (statusCode == HttpStatus.SC_NOT_MODIFIED) {//304,自从上次请求后，请求的网页未修改过
Entry entry = request.getCacheEntry();
if (entry == null) {
return new NetworkResponse(HttpStatus.SC_NOT_MODIFIED, null,
responseHeaders, true,
SystemClock.elapsedRealtime() - requestStart);
}
// A HTTP 304 response does not have all header fields. We
// have to use the header fields from the cache entry plus
// the new ones from the response.
// http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5
entry.responseHeaders.putAll(responseHeaders);
return new NetworkResponse(HttpStatus.SC_NOT_MODIFIED, entry.data,
entry.responseHeaders, true,
SystemClock.elapsedRealtime() - requestStart);
}否则，用缓存中数据包装成NetworkResponse返回就可以了。
接下来是处理301,302重定向地址错误
// Handle moved resources 网络资源被移动(301,302)，修改重定向地址
if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY || statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {
String newUrl = responseHeaders.get("Location");
request.setRedirectUrl(newUrl);
}再接下来是处理204之类的，没有响应主体的错误
// Some responses such as 204s do not have content. We must check.
if (httpResponse.getEntity() != null) {//返回响应主体
responseContents = entityToBytes(httpResponse.getEntity());//将主体转换byte[]形式
} else {//没有返回内容
// Add 0 byte response as a way of honestly representing a
// no-content request.
responseContents = new byte[0];
}最后，凡是http头有以上错误的(304除外)，抛出异常
if (statusCode < 200 || statusCode > 299) {//网络错误
throw new IOException();
}
是不是抛出异常就结束了呢？当然不是，因为volley还要根据request的RetryPolicy来进行重试，下面我们来看catch段的代码
} catch (SocketTimeoutException e) {
attemptRetryOnException("socket", request, new TimeoutError());
} catch (ConnectTimeoutException e) {
attemptRetryOnException("connection", request, new TimeoutError());
} catch (MalformedURLException e) {
throw new RuntimeException("Bad URL " + request.getUrl(), e);
} 可以看到，连接超时，地址格式错误，这些错误都会调用attemptRetryOnException()方法来进行重试
/**
* Attempts to prepare the request for a retry. If there are no more attempts remaining in the
* request's retry policy, a timeout exception is thrown.
* @param request The request to use.
* 准备重试请求.如果重试策略里面，没有新的目标，抛出异常
*/
private static void attemptRetryOnException(String logPrefix, Request<?> request,
VolleyError exception) throws VolleyError {
RetryPolicy retryPolicy = request.getRetryPolicy();//重试策略
int oldTimeout = request.getTimeoutMs();
try {
retryPolicy.retry(exception);//重试
} catch (VolleyError e) {
request.addMarker(
String.format("%s-timeout-giveup [timeout=%s]", logPrefix, oldTimeout));
throw e;
}
request.addMarker(String.format("%s-retry [timeout=%s]", logPrefix, oldTimeout));
}OK，重试策略实现了以后，我们再来看IOException是怎么处理的
catch (IOException e) {
int statusCode = 0;
NetworkResponse networkResponse = null;
if (httpResponse != null) {//没有响应，说明网络连接有问题
statusCode = httpResponse.getStatusLine().getStatusCode();
} else {
throw new NoConnectionError(e);
}
if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY ||
statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {//302,301
VolleyLog.e("Request at %s has been redirected to %s", request.getOriginUrl(), request.getUrl());
} else {
VolleyLog.e("Unexpected response code %d for %s", statusCode, request.getUrl());
}
if (responseContents != null) {//有响应内容
networkResponse = new NetworkResponse(statusCode, responseContents,
responseHeaders, false, SystemClock.elapsedRealtime() - requestStart);
if (statusCode == HttpStatus.SC_UNAUTHORIZED ||
statusCode == HttpStatus.SC_FORBIDDEN) {//401,请求要求身份验证;403,服务器拒绝请求
attemptRetryOnException("auth",//尝试重新请求
request, new AuthFailureError(networkResponse));
} else if (statusCode == HttpStatus.SC_MOVED_PERMANENTLY ||
statusCode == HttpStatus.SC_MOVED_TEMPORARILY) {//302,301
attemptRetryOnException("redirect",//尝试重定向请求
request, new AuthFailureError(networkResponse));
} else {
// TODO: Only throw ServerError for 5xx status codes.
throw new ServerError(networkResponse);//抛出服务器异常
}
} else {
throw new NetworkError(networkResponse);
}2，302,301错误，说明资源被重定向，做简单的记录
3，401,403错误，身份验证错误，重试
4，302,301错误，重试
OK，到此为止异常处理就已经说清楚了，这个network也说得比较清晰了。至于到底是怎么进行网络请求的，大家还是看下一篇文章吧。
扫一扫
681
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
