See #2 and #3. Although now maybe we it's the right time to do this.

Yeah, this is probably the right time to do this. The main question is how we want to deal with lysine-dev/okhttp#1305 . We can either downgrade to 2.1.0, or upgrade as is here and just know we can't run on older versions of Android until the issue is resolved.

Downgrading is what I am considering most strongly, so I can keep our internal code synced more closely with this repo, but that would be a problem the moment the issue isn't fixed and some other bug/feature is needed in a newer version of okhttp. Thus, I'm fine either way.

Thoughts?

Yeah. I would downgrade for now. We'll fix NPN in the next version.

Okay... Soo... Yeah...

Internally we are now patching NPN support back to okhttp, at least enough for our own usage. Since gRPC is currently requiring you to pass a pre-configured SslSocketFactory, you can use gRPC with NPN/ALPN without any support from okhttp. So there are no more blockers of using OkHttp 2.2.0.

Pulled as 0ca6584

@maniksurtani, I can't find a corporate CLA for Square. I was thinking y'all had one, but maybe I'm mistaken and y'all haven't filled out https://developers.google.com/open-source/cla/corporate ?

Let me chk with others @ Square

On 26 January 2015 at 16:04, Eric Anderson notifications@github.com wrote:

@maniksurtani https://github.com/maniksurtani, I can't find a corporate
CLA for Square. I was thinking y'all had one, but maybe I'm mistaken and
y'all haven't filled out
https://developers.google.com/open-source/cla/corporate ?

—
Reply to this email directly or view it on GitHub
#15 (comment).