thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuxuan Wang (Jira)" <>
Subject [jira] [Commented] (THRIFT-5164) Go middleware support
Date Mon, 27 Apr 2020 23:53:00 GMT


Yuxuan Wang commented on THRIFT-5164:

So after I created this ticket, we also implemented a middleware framework on the client side,
and I think we can contribute that to upstream as well (and reusing this ticket :P)
is the middleware definition part, basically we just wrap TClient into a WrappedTClient. It's
simpler than the server side as we don't have to make any breaking changes :)

A few lines down,
is an example of how we have a tracing middleware that auto creates a client child-span and
inject that into the context object (so it will be translate into THeaderProtocol over the
wire by the client) before send that to the client.

What do you think, [~dcelasun]?

> Go middleware support
> ---------------------
>                 Key: THRIFT-5164
>                 URL:
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Go - Library
>            Reporter: Yuxuan Wang
>            Assignee: Duru Can Celasun
>            Priority: Major
>              Labels: Breaking-Change
>             Fix For: 0.14.0
> I saw that this idea was discussed before in THRIFT-4553, but want to reopen the discussion
to see if there's a change of mind.
> We (Reddit) recently implemented TProcessor level middleware support in our Baseplate.go
library, and we think that our implementation is generic enough that it might make sense to
contribute that into the thrift library. The related implementation are all in this file:
is an example of how a tracing middleware is implemented.
> If we think that's a good idea, then we can contribute that into thrift repo (with renames,
of course). One implementation detail I'm not sure is that whether we want to expand the TProcessor
interface to also include ProcessorMap and AddToProcessorMap, or do we want to keep the two
iinterfaces separate.

This message was sent by Atlassian Jira

View raw message