Open tchernobog opened 1 day ago
Relates to #35 and #38.
For sure #35, not sure #38 is strongly linked.
An independent client implementation could always be used, I don't see it a hard dep for HTTP/3 support. Adding QUIC support to grpcxx shouldn't be extremely hard even right now, the main issue is the need to abstract code which uses TCP connections as QUIC is over UDP by default.
At that point, I would advise also supporting unix sockets for local IPC, since it makes sense to do the work only once.
Not saying we need to implement an HTTP/3 client in this issue, just wanted to keep related issues linked for future reference.
To achieve minimum viability as a Google gRPC substitute, grpcxx needs a client stub implementation to accompany its server-only implementation.
It should:
.grpcxx.pb.h
header