pjfanning opened a new issue, #931: URL: https://github.com/apache/pekko-grpc/issues/931
gRPC implementations offer client and server interceptors, which are the usual place for cross-cutting concerns such as auth, tracing, metrics and logging (e.g. grpc-java's `ClientInterceptor`/`ServerInterceptor`). In Pekko gRPC: - Server: there is no interceptor API. pekko-http directives around the generated handler can do some of this, but they don't see deserialized messages or per-call gRPC status in a uniform way. - Client, Netty backend: the only route is `channelBuilderOverrides` with `NettyChannelBuilder.intercept`. - Client, pekko-http backend: there is no hook at all. Proposal: decide between a client and server interceptor API that works the same way on both client backends, or a documented pattern (directives on the server; a request-builder or channel wrapper on the client). Cover unary and streaming calls, with Scala/Java parity. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
