[
https://issues.apache.org/jira/browse/THRIFT-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014304#comment-15014304
]
ASF GitHub Bot commented on THRIFT-3405:
----------------------------------------
Github user Jens-G commented on the pull request:
https://github.com/apache/thrift/pull/701#issuecomment-158191235
Committed per 13ac77daf031443ebdfbee02bad528f53b6212eb, this can be closed.
> Go THttpClient misuses http.Client objects
> ------------------------------------------
>
> Key: THRIFT-3405
> URL: https://issues.apache.org/jira/browse/THRIFT-3405
> Project: Thrift
> Issue Type: Improvement
> Components: Go - Library
> Affects Versions: 0.9.3
> Environment: Any
> Reporter: Justin Larrabee
> Assignee: Justin Larrabee
> Fix For: 1.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> THttpClient:Flush creates an http.Client object every time it is called. From
> the Go docs regarding the use of these client objects:
> "Clients and Transports are safe for concurrent use by multiple goroutines
> and for efficiency should only be created once and re-used."
> I suggest that the client used by the THttpTransport default to using either
> the http.DefaultClient or a package scoped default client. The transport
> should also accept a http.Client as an optional parameter so users of the
> library are free to control this behavior.
> With the current implementation I have run into issues when spinning up ~1000
> separate instances of the THttpClient for a load test application I have
> written. Switching to using a single shared http client resolved all
> connection issues I had.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
