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

Add option to share OkHttpClient #82

Closed
wants to merge 4 commits into from
Closed

Add option to share OkHttpClient #82

wants to merge 4 commits into from

Conversation

Jashepp
Copy link

@Jashepp Jashepp commented Mar 6, 2017

Potentially Fixes Issue #81

This adds an option to share an OkHttpClient instance over multiple sockets (from reconnect attempts, and etc). Defaults to false.
Let me know if the option can be named better, or if this can be done a better way.
This java-client-specific option can probably be mentioned in the readme under features?

Related to engine.io-client-java issue #81
It is already declared in Transport.Options
Related to engine.io-client-java issue #81
@shobhitpuri
Copy link

@unchosen Thanks so much for making the pul request? Would it be possible for you to please update the test case that's failing?

@Jashepp
Copy link
Author

Jashepp commented Mar 24, 2017

Odd.. In the first Travis CI tests ran on this PR, openjdk7 tests completed, yet the openjdk8 tests failed on the yeast test.
Yet now the tests are passing. It may have just been something random unrelated to this PR changes.

@@ -148,6 +151,7 @@ protected void onClose() {

public static class Options {

public storeOkHttpClient storeOkHttpClient = null;
Copy link
Collaborator

@b95505017 b95505017 Apr 23, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that use WebSocket.Factory interface is enough.

@b95505017 b95505017 closed this May 2, 2017
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

Successfully merging this pull request may close these issues.

3 participants