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 [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/c8c0c57d-2936-49a3-a272-d6cbedf2471f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
