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
HTTP/3 (with QUIC) promises significant efficiency gains over HTTP/2 which should be appealing for low latency applications. But there's no official spec for gRPC over HTTP/3 yet, although there's a draft (ref: grpc/grpc#19126).
We should explore the possibilities of supporting HTTP/3 along with HTTP/2. This might mean we have to do the client implementation as well (#35). What's the point in implementing HTTP/3 if no one can use it?
The text was updated successfully, but these errors were encountered:
HTTP/3 (with QUIC) promises significant efficiency gains over HTTP/2 which should be appealing for low latency applications. But there's no official spec for gRPC over HTTP/3 yet, although there's a draft (ref: grpc/grpc#19126).
We should explore the possibilities of supporting HTTP/3 along with HTTP/2. This might mean we have to do the client implementation as well (#35). What's the point in implementing HTTP/3 if no one can use it?
The text was updated successfully, but these errors were encountered: