-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
API for awaiting for stream reset on the reader #1870
Comments
What's the difference between waiting for a reset and reading? Can you link the spec for the WebTransport API you're referring to? |
Based on this: https://w3c.github.io/webtransport/ There is a
There are no relevant methods in the subclasses, so we can focus on the base classes:
The This is what I find missing in the Maybe I am misinterpreting my findings in the Web API, but then I need some tips on the topic of implementing this - but it seems like the Web API for WebTransport does have an API that can't be (simply) built on top of |
I find the web spec difficult to read (lots of circular definitions that don't actually specify anything useful), but the general idea you describe seems to make sense, and I don't oppose having such an API, even though its use may be niche. Our existing |
Yep,
Yeah, it is. I am not specializing on dealing with w3c stuff, had to dig through this just for the cross platform WebTransport, and it was veery tricky to spot this API even existing. |
Let me know if #1873 suits your requirements. Particular points of interest are |
Would be great to have an API that would allow waiting for a stream reset from the reader end. This is something that WebTransport API for the Web has, and it would be nice for supporting cross-platform interfaces for WebTransport (like
xwt
).WebTransport is relevant in the context of QUIC and
quinn
because WebTransport is a protocol that builds on top of HTTP3, which builds on top of QUIC.Concretely, I need this because I am having issues properly modeling interfaces at MOZGIII/xwt#152.
The text was updated successfully, but these errors were encountered: