[API Proposal]: [HTTP/3] Support multiple HTTP/3 connections #101535
Labels
api-suggestion
Early API idea and discussion, it is NOT ready for implementation
area-System.Net.Http
Milestone
Background and motivation
Similarly to HTTP/2, we want to introduce support for multiple HTTP/3 connections.
Both HTTP/2 and HTTP/3 have stream limits. As RFC Bidirectional Streams suggests, the minimum is 100, which is the current Kestrel default. As #35088 states, this becomes a bottleneck for service-to-service communication, e.g. gRPC.
Implementation depends on #101534.
Original issue: #51775
For comparison with HTTP/2 see the original issue #35088
API Proposal
API Usage
Alternative Designs
N/A
Risks
None. It's an opt-in, default will be
false
, keeping the original behavior in place.The text was updated successfully, but these errors were encountered: