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

Dylan Wen updated THRIFT-3251:
------------------------------
    Description: 
There is a lack of http transport for server in Go lib, so the server could not 
communicate with client running http transport, e.g., client runs the Go code  
lib/go/thrift/http_client.go, or C++ async client which usually runs along with 
libevent and http transport.

Some code similar to lib/cpp/src/thrift/transport/THttpTransport.cpp needs to 
be added to Go lib, in order to run a server written in Go to communicate with 
these http transport client.

  was:
There is a lack of http transport for server in Go lib, so the server could not 
communicate with client running http transport, e.g., client runs the Go code  
lib/go/thrift/http_client.go, or C++ async client which usually runs along with 
libevent and http transport.

Some code which is similar to lib/cpp/src/thrift/transport/THttpTransport.cpp 
needs to be added to Go lib, in order to run a server written in Go to 
communicate with these http transport client.


> Add http transport for server to Go lib
> ---------------------------------------
>
>                 Key: THRIFT-3251
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3251
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Go - Library
>    Affects Versions: 0.9.2
>            Reporter: Dylan Wen
>            Priority: Minor
>
> There is a lack of http transport for server in Go lib, so the server could 
> not communicate with client running http transport, e.g., client runs the Go 
> code  lib/go/thrift/http_client.go, or C++ async client which usually runs 
> along with libevent and http transport.
> Some code similar to lib/cpp/src/thrift/transport/THttpTransport.cpp needs to 
> be added to Go lib, in order to run a server written in Go to communicate 
> with these http transport client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to