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

Possibility to have a shared HttpTransport #103

Closed
XtraSonic opened this issue Jul 21, 2020 · 1 comment
Closed

Possibility to have a shared HttpTransport #103

XtraSonic opened this issue Jul 21, 2020 · 1 comment

Comments

@XtraSonic
Copy link
Contributor

In the google documentation of HttpTransport it is mentioned that

For maximum efficiency, applications should use a single globally-shared instance of the HTTP transport.

GoogleHttpClient creates a new NetHttpTransport each time a new instance is created. According to the google documentation, this results in loss of efficiency. A solution for this would be to be able to give as a parameter an existing HttpTransport and use that in stead of creating a new NetHttpTransport each time.

@XtraSonic
Copy link
Contributor Author

Solved in #113

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

No branches or pull requests

1 participant