为什么Volley Library通常与okHttp Library结合使用？

Question

Why is Volley usually combined with okHttp? Why is it done like this?

eg:

   OkHttpClient client = new OkHttpClient();
   client.networkInterceptors().add(new StethoInterceptor());
   mRequestQueue = Volley.newRequestQueue(context, new OkHttpStack(client));

Answer 1

Volley needs an HttpStack when you create the RequestQueue .

If you don't provide one, Volley will create an stack depending on your API level: If you are running API 9 or below it'll be based on the AndroidHttpClient. If you are running API 10 or above it'll be based on HttpURLConnection.

OkHttp is an modern, fast and efficient Http client which supports HTTP/2 and SPDY and does a lot of stuff for you like connection pooling, gziping, caching… and so on. OkHttp acts like the transport layer.

OkHttp uses Okio , a library that complements java.io and java.nio to make it much easier to access, store, and process your data.

For those reasons I recommend you to use and OkHttp Stack. I'm using this one that does not use okhttp-urlconnection.

I've written an article about using OkHttp, Volley and Gson for Android networking that you might find interesting.

Answer 2

阅读本文为什么okhttp适合运输 - 然后你会知道为什么它经常与凌空相结合