The problem: I would like to not rely on the Envoy proxy for other languages like python and rust.
Has there been a discussion of putting on the roadmap a c client and server library that would be a GRPC-Web proxy library? Then a client or server implementation could integrate middleware to <LanguageX> GRPC Client <In-process Proxy--> GRPC-Web --> GRPC-Web Server and GRPC-Web Client --> GRPC-Web Server <In-process Proxy--> GRPC Server. The hope would be that a common code base with an interoperability test suite, would be able to unlock the capability and adoption for many languages. Optionally if architected the right way could handle also managing a Non-Binary Message Encoding ideally JSON which might unlock the interoperability with other rest ecosystem tooling which would be desirable for some use-cases. If you have a reference to any discussions I would be interested in that. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8031aab3-6191-4b72-b1ea-8ed111ec25f5n%40googlegroups.com.
