[
https://issues.apache.org/jira/browse/THRIFT-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635617#comment-14635617
]
Adam Beberg commented on THRIFT-3251:
-------------------------------------
Curious why you implemented HTTP from scratch.
My approach for THRIFT-3186 (which I should finish testing) is to use the
standard net/http Handler model in Go, producing a http.Handler (vs a TServer),
which allows Thrift services to coexist with other HTTP handlers in the code
(e.g. existing REST interfaces) on different paths, with multi-threading, TLS,
etc already there.
It's different then the SImpleServer approach, because listen/accept/open/close
makes little sense in the context of HTTP.
> 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)
