Skip to content
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

okhttp-ws is deprecated. #22

Open
tannerpreiss opened this issue Jan 30, 2017 · 0 comments
Open

okhttp-ws is deprecated. #22

tannerpreiss opened this issue Jan 30, 2017 · 0 comments

Comments

@tannerpreiss
Copy link

It appears that okhttp-ws is deprecated and square moved it into the larger okhttp package. We should look to move to the okhttp library because it could be a reason to the timeouts client side.

https://medium.com/square-corner-blog/web-sockets-now-shipping-in-okhttp-3-5-463a9eec82d1#.scgjcyomh

From okhttp 3.5.0 Release notes:
https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-350

Web Sockets are now a stable feature of OkHttp. Since being introduced as a beta feature in OkHttp 2.3 our web socket client has matured. Connect to a server's web socket with OkHttpClient.newWebSocket(), send messages with send(), and receive messages with the WebSocketListener.

The okhttp-ws submodule is no longer available and okhttp-ws artifacts from previous releases of OkHttp are not compatible with OkHttp 3.5. When upgrading to the new package please note that the WebSocket and WebSocketCall classes have been merged. Sending messages is now asynchronous and they may be enqueued before the web socket is connected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant