fishy opened a new pull request #2189:
URL: https://github.com/apache/thrift/pull/2189


   Client: go
   
   We separated timeout in go's TSocket into connect timeout and socket
   timeout in 81334cd, this change does the same for TSSLSocket to keep
   them consistent.
   
   Also rename the arg in NewTSocketFromConnTimeout from connTimeout to
   socketTimeout, because in that function we already have a connection,
   so connect timeout is never used again. The timeout passed into that
   function is really for socket timeout, not connect timeout. The name of
   that function actually means "New TSocket From Conn (with) Timeout", not
   "New TSocket From ConnTimeout" (I guess that's where the original
   confusion came from).
   
   Also add the missing change note for the breaking change.
   
   <!-- Explain the changes in the pull request below: -->
     
   
   <!-- We recommend you review the checklist/tips before submitting a pull 
request. -->
   
   - [x] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket?  (not 
required for trivial changes)
   - [x] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit?  (not required, but 
preferred)
   - [x] Did you do your best to avoid breaking changes?  If one was needed, 
did you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to