You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2014/11/11 00:15:38 UTC

[jira] [Resolved] (THRIFT-2812) Go server adding redundant buffering layer

     [ https://issues.apache.org/jira/browse/THRIFT-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer resolved THRIFT-2812.
--------------------------------
    Resolution: Fixed

Committed, thanks for catching this.

> 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
>    Affects Versions: 0.9.2
>            Reporter: Stephen Marbowitz
>            Assignee: Jens Geyer
>             Fix For: 0.9.3
>
>
> 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)