Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement support for unary interceptor chaining. #152

Merged
merged 2 commits into from
Sep 6, 2023
Merged

Implement support for unary interceptor chaining. #152

merged 2 commits into from
Sep 6, 2023

Commits on Aug 25, 2023

  1. client: implement UnaryClientInterceptor chaining. 

    Add a WithChainUnaryClientInterceptor client option to allow
using more that one client call interceptor which will then
get chained and invoked in the order given.

This should allow us to implement opentelemetry instrumentation
as interceptors while allowing users to keep intercepting their
client calls for other reasons at the same time.

Signed-off-by: Krisztian Litkey <[email protected]>
    @klihub
    klihub committed Aug 25, 2023
    Configuration menu
    Copy the full SHA
    f984c9b View commit details
    Browse the repository at this point in the history

  2. server: implement UnaryServerInterceptor chaining. 

    Add a WithChainUnaryServerInterceptor server option to allow
using more that one server side interceptor which will then
get chained and invoked in the order given.

This should allow us to implement opentelemetry instrumentation
as interceptors while allowing users to keep intercepting their
server side calls for other reasons at the same time.

Signed-off-by: Krisztian Litkey <[email protected]>
    @klihub
    klihub committed Aug 25, 2023
    Configuration menu
    Copy the full SHA
    40f227d View commit details
    Browse the repository at this point in the history