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

Implement OkHttp-based HTTP client transport #824

sbordet opened this Issue Jan 24, 2019 · 1 comment


None yet
1 participant
Copy link

sbordet commented Jan 24, 2019

It would be great to have a OkHttp-based HTTP transport.


This comment has been minimized.

Copy link
Member Author

sbordet commented Jan 24, 2019

Allowing pluggable HTTP client transport requires a restructuring of the Maven coordinates, Maven modules and JPMS modules, since now it's all hardcoded to be a single artifact depending on jetty-client.
We would need a common module, a jetty-specific module, a okhttp-specific module, a test module that tests both implementations, etc.
Likely client applications will break because they will have now to specify explicitly a dependency on one implementation, and the class name of the client transport will be different, probably both in name and package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment