Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update HTTP/2 and HTTP/3 duplex content streams to use DuplexStream #51432

Open
scalablecory opened this issue Apr 17, 2021 · 2 comments
Open
Labels
area-System.Net.Http enhancement Product code improvement that does NOT require public API changes/additions
Milestone

Comments

@scalablecory
Copy link
Contributor

The HTTP/2 and HTTP/3 duplex streams could implement DuplexStream.

I don't think there is technically anything blocking us from doing so for HTTP/1 as well, but we don't support duplex in HTTP/1 right now.

@scalablecory scalablecory added enhancement Product code improvement that does NOT require public API changes/additions area-System.Net.Http labels Apr 17, 2021
@scalablecory scalablecory added this to the Future milestone Apr 17, 2021
@ghost
Copy link

ghost commented Apr 17, 2021

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

The HTTP/2 and HTTP/3 duplex streams could implement DuplexStream.

I don't think there is technically anything blocking us from doing so for HTTP/1 as well, but we don't support duplex in HTTP/1 right now.

Author: scalablecory
Assignees: -
Labels:

area-System.Net.Http, enhancement

Milestone: Future

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 17, 2021
@ManickaP ManickaP removed the untriaged New issue has not been triaged by the area owner label Apr 22, 2021
@ManickaP
Copy link
Member

Triage: not blocking 6.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Net.Http enhancement Product code improvement that does NOT require public API changes/additions
Projects
None yet
Development

No branches or pull requests

2 participants