[
https://issues.apache.org/jira/browse/THRIFT-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Marbowitz updated THRIFT-2812:
--------------------------------------
Description: THRIFT-2791 incorrectly assumed there was no way to do
buffered sockets on the server. The solution is to simply use a
TBufferedTransportFActory and give it to the server at creation time. Can we
please revert that patch? Any code that was previously using buffered server
sockets now has an extra layer of buffering. I consider this a breaking change.
(was: THRIFT-2791 incorrectly assumed there was no way to do buffered sockets
on the server. The solution is to simply use a TBufferedTransportFActory and
give it to the server at creation time. Can we please revert that patch?)
> Go server adding redundant buffering layer
> ------------------------------------------
>
> Key: THRIFT-2812
> URL: https://issues.apache.org/jira/browse/THRIFT-2812
> Project: Thrift
> Issue Type: Bug
> Components: Go - Library
> Reporter: Stephen Marbowitz
>
> THRIFT-2791 incorrectly assumed there was no way to do buffered sockets on
> the server. The solution is to simply use a TBufferedTransportFActory and
> give it to the server at creation time. Can we please revert that patch? Any
> code that was previously using buffered server sockets now has an extra layer
> of buffering. I consider this a breaking change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
