[
https://issues.apache.org/jira/browse/THRIFT-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188349#comment-16188349
]
ASF GitHub Bot commented on THRIFT-4285:
----------------------------------------
Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1382
We support go back to version 1.2.1 or 1.4.3 (I can't remember which, but I
think 1.2.1 is on trusty). That said, I'm in the middle of reworking the
docker images to be as stock as possible, and adding an ubuntu-artful one which
has go 1.8.3 on it. I don't think we can unilaterally require go 1.9 at this
point without causing some pain, but I'm not sure. I haven't been that
involved in the go ecosystem.
> Pull generated send/recv into library to allow behaviour to be customised
> -------------------------------------------------------------------------
>
> Key: THRIFT-4285
> URL: https://issues.apache.org/jira/browse/THRIFT-4285
> Project: Thrift
> Issue Type: Improvement
> Components: Go - Compiler, Go - Library
> Reporter: Chris Bannister
> Assignee: Chris Bannister
> Attachments: 0001-go-pull-generated-send-recv-into-lib-v6.patch,
> 0001-go-pull-generated-send-recv-into-lib-v7.patch
>
>
> Currently it is difficult to change how thrift writes messages onto the
> transport because they are in the generated code. Instead the generated
> send/recv methods should be in the library. This will greatly simplify the
> client code and remove many duplicate methods whilst allowing users more
> flexibility to implement connection pools and other features such as THeader.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
