[GitHub] thrift issue #1440: Enhancement binary_protocol with frametransport

[zhiyu-he]

Github user zhiyu-he commented on the issue:

    https://github.com/apache/thrift/pull/1440
  
    @jeking3 
    but the difference between buffer-transport and frame_transport， is only 
the data-length.
    i think thrift transport only use for raw-socket read&write.
    
    within golang, it's inefficient and cost more cpu time.
    
     in binary_protocol,  e.g for int64,  
int64->temp-buf(binary_protol)->buf(transport-buf)->socket
    this is not go enough for efficiency
    so i want optimize this part。


---