Glad to see a Python interceptor proposal! It seems to follow the pattern used in grpc-go, with APIs for RPC types (unary_unary, unary_stream, etc) rather than APIs for phases of the request/response (sendMessage, close, etc) like grpc-java. Can you describe the overall strategy for interceptor APIs in the supported languages?
I'm also curious about the names of the 4 RPC types. I'm familiar with these names from the Node implementation: Unary ClientStreaming ServerStreaming Bidirectional And from searching the grpc/grpc codebase I see those names in other implementations. Is there an interest in standardizing the names of RPC types across languages? On Monday, October 2, 2017 at 5:07:11 AM UTC-7, Mehrdad Afshari wrote: > > I've submitted a gRFC for supporting client and server interceptors in > Python: > > https://github.com/grpc/proposal/pull/39 > > Implementation: https://github.com/grpc/grpc/pull/12778 > > Feedback is appreciated. Per the gRFC process, please keep discussion in > this thread. > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/546d9ea4-239a-4c6c-bb03-81ccd55cf32c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
