Go implementation of a multiplexing and framing protocol for RPC calls
TChannel is a network protocol that supports:
This protocol is intended to run on datacenter networks for inter-process communication.
TChannel frames have a fixed-length header and 3 variable-length fields. The underlying protocol does not assign meaning to these fields, but the included client/server implementation uses the first field to represent a unique endpoint or function name in an RPC model. The next two fields can be used for arbitrary data. Some suggested way to use the 3 fields are:
Note, however, that the only encoding supported by TChannel is UTF-8. If you want JSON, you'll need to stringify and parse outside of TChannel.
This design supports efficient routing and forwarding: routers need to parse the first or second field, but can forward the third field without parsing.
There is no notion of client and server in this system. Every TChannel instance is capable of making and receiving requests, and thus requires a unique port on which to listen. This requirement may change in the future.
See the protocol specification for more details.