Thrift proxy

Thrift Request Metadata

The and TWITTER protocol support metadata. In particular, the supports informational key/value pairs and the Twitter protocol transmits tracing and request context data.

Header transport key/value pairs are available for routing as .

Client Identifier

The ClientId’s name field (nested in the RequestHeader client_id field) becomes the :client-id header.

The RequestHeader dest field becomes the :dest header.

Delegations

Request metadata that is available for routing (see above) is automatically converted between wire formats when translation between downstream and upstream connections occurs. Twitter protocol request contexts, client id, destination, and delegations are therefore presented as Header transport key/value pairs, named as above. Similarly, Header transport key/value pairs are presented as Twitter protocol RequestContext values, unless they match the special names described above. For instance, a downstream Header transport request with the info key “:client-id” is translated to an upstream Twitter protocol request with a ClientId value.