Volley源码分析(三)NetWorkDispatcher分析

最新推荐文章于 2022-02-13 12:19:44 发布

weixin_30642267

最新推荐文章于 2022-02-13 12:19:44 发布

阅读量101

点赞数

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/qifengshi/p/7069685.html

本文深入分析了NetWorkDispatcher的工作原理，它继承自Thread类，在run方法中通过无限循环处理网络请求。文章详细介绍了如何从队列中取出请求，判断请求状态，执行网络请求并获取响应，处理304状态码，解析响应内容，缓存结果以及最终将结果发送回主线程。

NetWorkDispatcher分析

NetWorkDispatcher和CacheDispatcher一样，继承于Thread,在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);
            }
        }
    }

其主要的流程如下：首先从队列中取出request,然后判断该request是否取消了，如果取消就结束，然后调用network的performRequest方法进行请求得到netWorkResponse，判断该response是否是304，如果是的话，或者已经发送了相同的response，就不在发送了。因为304是只返回了header无body,因为该request的结果已经缓存了。然后就进行networkresponse的解析，然后判断该request是否需要缓存，如果需要就放入cache中，然后mDelivery.postResponse(request, response);