-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plan upgrade to OkHttp 3? #2999
Comments
We didn't really. We've manually "shaded" most of OkHttp that we use such that the okhttp dependency is just for our surface API for specifying TLS settings (via ConnectionSpec). We could probably have OkHttpChannelBuilder support both ConnectionSpec from OkHttp 2 and 3 simultaneously. It would mean depending on both versions, but when using ProGuard only one would be used. It's not clear whether that just gives us a "nice feeling" or whether it actually would benefit someone. |
It doesn't sound like this provides a tangible benefit, so closing. It'd be easy to convince me otherwise, though. So if this would benefit you, say so and we will consider it. Also mention whether depending on both OkHttp 2 and OkHttp 3 would be a solution for you. |
In Android We are so used to okhttp for handling all our rest call needs . It will benefit us from learning point of view. |
As title.
The text was updated successfully, but these errors were encountered: