Add OkHttp as a ConnectionProvider #47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* clean imports * package visibility for all provider implementation (force instantiation of the connection provider from the Stomp class only) * Subscriber lists are final
The main motivation is to make possible to the user of the library to pass its own websocket client: this way, the developer can configure and/or enable/disable additionnal features of the client (ping to keep the connection alive with OkHttp, or configure timeouts for example)
|
Great job! It's worked on my project |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I've added a new ConnectionProvider based on https://github.com/square/okhttp, since the WebSocket API of OkHttp is now stable.
The implementation is really close to what you have done on the existing
WebSocketsConnectionProviderLet me know if this works out for you !