Volley源码阅读之网络分发器（NetworkDispatcher）的工作原理

Volley的NetworkDispatcher本质上是一个线程类，它继承自Thread，目的在于提供一个线程来分发请求队列里面的请求：

public class NetworkDispatcher extends Thread

先来看看NetworkDispacher有哪些成员变量以及作用

 /** 请求队列 */
    private final BlockingQueue<Request<?>> mQueue;
    /** 处理请求*/
    private final Network mNetwork;
    /** 缓存响应内容 */
    private final Cache mCache;
    /** 传递响应内容和错误 */
    private final ResponseDelivery mDelivery;
    /** 标记NetworkDispatcher是否被中断 */
    private volatile boolean mQuit = false;

NetworkDispatcher内部维护了一个请求阻塞队列和响应内容缓存区。请求队列用于缓存请求，NetworkDispatcher会从请求队列中依次取出请求并执行；响应内容缓存区内部维护了一个类似Map一样的数据结构，用来缓存执行请求返回来的响应内容。
既然NetworkDispatcher是一个线程类，那么我们最主要关心的就是run方法了。下面我们来看看NetworkDispatcher的run方法到底干了什么：
首先，对线程设置优先级

 Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);

接着一个while循环不断从请求队列中取出请求来执行，并把执行结果返回给调用者。
NetworkDispatcher是如何缓存请求执行的响应内容的呢？原理其实非常的简单。首先从请求队列取出请求，如果请求没有被中断或者取消，那么执行请求获取响应内容。如果响应内容和上次获取的内容没有改变，或者次响应内容已经传递给调用者了，那么就不用再一次缓存内容，否则解析出响应内容然后判断它是否符合缓存条件（请求有标记要缓存并且响应内容解析出来的主体不为空）来判断是否需要缓存。
下面是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);
            }
        }
    }