You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
#38 is related in the sense there aren't any HTTP/3 gRPC clients at the moment (at least not that I'm aware of), so if we implement HTTP/3 there must be a client to use it with.
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
headerThe text was updated successfully, but these errors were encountered: