Volley(四) Volley框架(从源码角度分析)

最新推荐文章于 2024-02-20 16:38:15 发布

90后小吕

最新推荐文章于 2024-02-20 16:38:15 发布

阅读量464

点赞数

本文链接：https://blog.csdn.net/qq_20607305/article/details/48312833

版权

Volley现在大家想必都已经会是用了，光使用是不够的。我们还要弄清楚Volley整个的框架，开始我也是迷迷糊糊的以为会使用就可以了，但是毕竟安卓开源的吗咱们要学习一下大神们的思想，这样也有助于咱们更好的理解Volley

盗用别人一张Volley框架图 Volley官方也有一张图我感觉这个比较详细就拿过来了

我们看着这个图是不是感觉很乱，其实我们可以把这张图仔细的分为三部分来看

第一部分：main thread 主线程（请求队列）

第二部分：cache thread 缓存线程

第三部分：网络线程

这样我们从头开始分析Volley ，我们知道Volley使用的时候第一行代码是Volley.newRequestQueue(context) 这样我们得到一个RequestQueue 我们看一下源代码

public static RequestQueue newRequestQueue(Context context) {
return newRequestQueue(context, null);
}

这里我们调用了 newRequestQueue 这个方法重载不过这个方法我们默认给第二个参数为null 好我们看一下带有两个参数的newRequestQueue

public static RequestQueue newRequestQueue(Context context, HttpStack stack) {
File cacheDir = new File(context.getCacheDir(), DEFAULT_CACHE_DIR);
String userAgent = "volley/0";
try {
String packageName = context.getPackageName();
PackageInfo info = context.getPackageManager().getPackageInfo(packageName, 0);
userAgent = packageName + "/" + info.versionCode;
} catch (NameNotFoundException e) {
}
if (stack == null) {
if (Build.VERSION.SDK_INT >= 9) {
stack = new HurlStack();
} else {
stack = new HttpClientStack(AndroidHttpClient.newInstance(userAgent));
}
}
Network network = new BasicNetwork(stack);
RequestQueue queue = new RequestQueue(new DiskBasedCache(cacheDir), network);
queue.start();
return queue;
}

(下面我把这段代码拆开给大家讲解一下)

我当时看到这个源码的时候第一眼我就对第二个参数情有独钟了因为我们知道现在大家都在讨论OkHttpClient 有的人说我用Volley 有的人说我用OkHttpClient 那么问题来了问什么我们不用Volley+OkHttpClient呢只要我们自己自定义我们自己的 HttpStack 就完全可以用Volley+OkHttpClient 好了扯远了这个问题大家自己去查资料

好咱们看一下这个HttpStack

public interface HttpStack {
/**
* Performs an HTTP request with the given parameters.
*
* <p>A GET request is sent if request.getPostBody() == null. A POST request is sent otherwise,
* and the Content-Type header is set to request.getPostBodyContentType().</p>
*
* @param request the request to perform
* @param additionalHeaders additional headers to be sent together with
* {@link Request#getHeaders()}
* @return the HTTP response
*/
public HttpResponse performRequest(Request<?> request, Map<String, String> additionalHeaders)
throws IOException, AuthFailureError;
}

其实就是一个接口没什么神奇的其实这个HttpStack对象才是真正的去网络拿回我们需要的数据 (题外话我们定义自己的HttpStack 把这个作为传输层这样就可以使用Volley+OkHttpClient 大家有时间去研究不扯了我就是顺便说一句)

好我们不要纠结这个HttpStack 我们还是看上面这个newRequestQueue方法我们看第10行判断stack是不是null

if (stack == null) {
if (Build.VERSION.SDK_INT >= 9) {
stack = new HurlStack();
} else {
stack = new HttpClientStack(AndroidHttpClient.newInstance(userAgent));
}
}

这里我们会判断手机系统版本号是不是大于9 是创建一个HurlStack实例不是创建一个HttpClientStack ，其实HurlStack内部就是使用HttpURLConnection进行网络通讯的，而HttpClientStack 的内部是使用HttpClient进行通

讯的 (其实Volley最终和网络交互使用的还是HttpURLConnection和HttpClient)

我们接着看下面几行代码

Network network = new BasicNetwork(stack);
RequestQueue queue = new RequestQueue(new DiskBasedCache(cacheDir), network);
queue.start();
return queue;

我们创建一个Network对象（NetWork也是一个接口）在Volley中的实现类是BasicNetwork 我们可以看一下这个源码

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;
}

这个 Network我们稍微了解就行了就一句话这个NetWork的主要作用就是根据我们传入的HttpStack对象来处理网络请求的

还是看我们上一段代码我们new了一个RequestQueue紧接着调用了它的start方法好我们就看一下start方法

public void start() {
stop(); // Make sure any currently running dispatchers are stopped.
// Create the cache dispatcher and start it.
mCacheDispatcher = new CacheDispatcher(mCacheQueue, mNetworkQueue, mCache, mDelivery);
mCacheDispatcher.start();
// Create network dispatchers (and corresponding threads) up to the pool size.
for (int i = 0; i < mDispatchers.length; i++) {
NetworkDispatcher networkDispatcher = new NetworkDispatcher(mNetworkQueue, mNetwork,
mCache, mDelivery);
mDispatchers[i] = networkDispatcher;
networkDispatcher.start();
}
}

这段代码我们好好分析一下首先我们创建了一个 CacheDispatcher（缓存线程）然后在一个for循环里面创建了NetworkDispatcher（网络线程）默认的会执行四次所以我们调用Volley.newRequestQueue(context)之后默认会创建五个线程一个缓存线程四个网络线程

得到RequestQueue之后我们就得创建我们的Request了，然后调用RequestQueue的add()方法将Request传入就可以完成网络请求操作了我们来看一下add方法的源码

public <T> Request<T> add(Request<T> request) {
// Tag the request as belonging to this queue and add it to the set of current requests.
request.setRequestQueue(this);
synchronized (mCurrentRequests) {
mCurrentRequests.add(request);
}
// Process requests in the order they are added.
request.setSequence(getSequenceNumber());
request.addMarker("add-to-queue");
// If the request is uncacheable, skip the cache queue and go straight to the network.
if (!request.shouldCache()) {
mNetworkQueue.add(request);
return request;
}
// Insert request into stage if there's already a request with the same cache key in flight.
synchronized (mWaitingRequests) {
String cacheKey = request.getCacheKey();
if (mWaitingRequests.containsKey(cacheKey)) {
// There is already a request in flight. Queue up.
Queue<Request<?>> stagedRequests = mWaitingRequests.get(cacheKey);
if (stagedRequests == null) {
stagedRequests = new LinkedList<Request<?>>();
}
stagedRequests.add(request);
mWaitingRequests.put(cacheKey, stagedRequests);
if (VolleyLog.DEBUG) {
VolleyLog.v("Request for cacheKey=%s is in flight, putting on hold.", cacheKey);
}
} else {
// Insert 'null' queue for this cacheKey, indicating there is now a request in
// flight.
mWaitingRequests.put(cacheKey, null);
mCacheQueue.add(request);
}
return request;
}
}

我们直接看11行先判断我们的Request是不是可以缓存如果不可以缓存，直接调用mNetworkQueue.add(request); 将请求放到网络线程中默认的是都可以缓存的好如果现在我们的请求都缓存起来了现在缓存线程就可以运行了我们直接看缓存线程里面的run方法

public class CacheDispatcher extends Thread {
……
@Override
public void run() {
if (DEBUG) VolleyLog.v("start new dispatcher");
Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);
// Make a blocking call to initialize the cache.
mCache.initialize();
while (true) {
try {
// Get a request from the cache triage queue, blocking until
// at least one is available.
final Request<?> request = mCacheQueue.take();
request.addMarker("cache-queue-take");
// If the request has been canceled, don't bother dispatching it.
if (request.isCanceled()) {
request.finish("cache-discard-canceled");
continue;
}
// Attempt to retrieve this item from cache.
Cache.Entry entry = mCache.get(request.getCacheKey());
if (entry == null) {
request.addMarker("cache-miss");
// Cache miss; send off to the network dispatcher.
mNetworkQueue.put(request);
continue;
}
// If it is completely expired, just send it to the network.
if (entry.isExpired()) {
request.addMarker("cache-hit-expired");
request.setCacheEntry(entry);
mNetworkQueue.put(request);
continue;
}
// We have a cache hit; parse its data for delivery back to the request.
request.addMarker("cache-hit");
Response<?> response = request.parseNetworkResponse(
new NetworkResponse(entry.data, entry.responseHeaders));
request.addMarker("cache-hit-parsed");
if (!entry.refreshNeeded()) {
// Completely unexpired cache hit. Just deliver the response.
mDelivery.postResponse(request, response);
} else {
// Soft-expired cache hit. We can deliver the cached response,
// but we need to also send the request to the network for
// refreshing.
request.addMarker("cache-hit-refresh-needed");
request.setCacheEntry(entry);
// Mark the response as intermediate.
response.intermediate = true;
// Post the intermediate response back to the user and have
// the delivery then forward the request along to the network.
mDelivery.postResponse(request, response, new Runnable() {
@Override
public void run() {
try {
mNetworkQueue.put(request);
} catch (InterruptedException e) {
// Not much we can do about this.
}
}
});
}
} catch (InterruptedException e) {
// We may have been interrupted because it was time to quit.
if (mQuit) {
return;
}
continue;
}
}
}
}

这段代码很长我们没必要每一行都搞明白我们看主要的地方就可以了首先我们看到一个while循环证明我们这个线程、

、一直运行的我们看23 24行23行我们在缓存中取出对应请求的缓存结果如果为null 则把这个请求放到网络请求队列

我们看31行然后我们判断这个缓存结果是不是已经过期如果过期了我们同样的吧Request放入到网络请求队列中如

果缓存结果不为null 并且没有过期我们直接返回缓存的结果 39行调用 parseNetworkResponse对数据进行解析

在往后就是回调数据了这个方法的实现是交给Request的子类来完成的，因为不同种类的Request解析的方式也肯

定不同。我们自定义的Request中这个方法是必须实现的因为不同的Request解析方式不同

整个就是缓存线程现在我们来看一下网络线程

ublic class NetworkDispatcher extends Thread {
……
@Override
public void run() {
Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);
Request<?> request;
while (true) {
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) {
parseAndDeliverNetworkError(request, volleyError);
} catch (Exception e) {
VolleyLog.e(e, "Unhandled exception %s", e.toString());
mDelivery.postError(request, new VolleyError(e));
}
}
}
}

现在一看头大了这什么跟什么啊不要急我们没必要每一个都弄得非常清楚我们找到里面重点(其实里面我也很多不

懂的。。。) 我们看28行这个时候会调用performRequest 去请求网络这个NetWork刚才我们说了这是一个接口

Volley具体的实现是BasicNetwork 这个源码咱们就不讲了都是一些网络请求细节方面的东西有的不用搞太懂理解部

分我们会使用就可以了（主要是对我这个一年多安卓的来说源码有的不是很明白）我们看37行和41行网络请求返回给

我们一个NetworkResponse然后我们对这个对象进行解析以及缓存刚才缓存线程已经说了我们这个具体的解析是子

类来完成的因为不同的Request解析方式肯定不同最后我们调用 postResponse进行回调我们解析的数据

我们看一下postResponse方法

public void postResponse(Request<?> request, Response<?> response, Runnable runnable) {
request.markDelivered();
request.addMarker("post-response");
mResponsePoster.execute(new ResponseDeliveryRunnable(request, response, runnable));
}

我们调用了execute方法这里有个参数ResponseDeliveryRunnable 我们看一下这个源码

private class ResponseDeliveryRunnable implements Runnable {
private final Request mRequest;
private final Response mResponse;
private final Runnable mRunnable;
public ResponseDeliveryRunnable(Request request, Response response, Runnable runnable) {
mRequest = request;
mResponse = response;
mRunnable = runnable;
}
@SuppressWarnings("unchecked")
@Override
public void run() {
// If this request has canceled, finish it and don't deliver.
if (mRequest.isCanceled()) {
mRequest.finish("canceled-at-delivery");
return;
}
// Deliver a normal response or error, depending.
if (mResponse.isSuccess()) {
mRequest.deliverResponse(mResponse.result);
} else {
mRequest.deliverError(mResponse.error);
}
// If this is an intermediate response, add a marker, otherwise we're done
// and the request can be finished.
if (mResponse.intermediate) {
mRequest.addMarker("intermediate-response");
} else {
mRequest.finish("done");
}
// If we have been provided a post-delivery runnable, run it.
if (mRunnable != null) {
mRunnable.run();
}
}
}