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.

Sign up for GitHub

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

Jump to bottom

Mandate unidirectional QUIC streams #333

Closed
mfoltzgoogle opened this issue May 20, 2024 · 0 comments · Fixed by #335
Closed

Mandate unidirectional QUIC streams #333

mfoltzgoogle opened this issue May 20, 2024 · 0 comments · Fixed by #335
Assignees
@mfoltzgoogle
Labels
QUIC v1-spec

Comments

@mfoltzgoogle
Copy link
Contributor

Unidirectional QUIC streams appear to be sufficient to implement the spec and are simpler to manage. Unlike bidirectional streams, the source of the stream can hang up and not wait for the target.

However, the spec should clarify that unidirectional streams should be used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mfoltzgoogle mfoltzgoogle

Labels
QUIC v1-spec
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify QUIC stream usage. w3c/openscreenprotocol
1 participant
@mfoltzgoogle