This feature would definitely need a gRFC, see this repo <https://github.com/grpc/proposal>. I would suggest clarifying your ideas for the design a bit further, then posting them there to get feedback from gRPC team and from security team
On Tuesday, April 3, 2018 at 4:01:54 AM UTC-7, mira....@gmail.com wrote: > > We are using (runtime) interchangeable implementation of tls (read we > update it during runtime) > This means we have to do some reference counting on loaded tls > implementation, restart long-running connection to allow update and hack > grpc sources to allow us to do this. > As upstream changes are always better option can anyone suggest a best way > to do this ? (so I can do pull request to upstream and it would be > acceptable by community) > I would like this as an option in channel properties (currently we have > this hacked into ssl_config structure), but channel arguments are usually > not passed directly into tsi but parsed and passed. > > WDYT ? > -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/9e1e46e9-521c-43fa-94f3-fa36c8949f50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
