-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Tracking Issue] Experimental WebTransport Transport #1717
Comments
@marten-seemann @MarcoPolo @p-shahi : I created this issue so we can taskify the WebTrasnport work. Please go ahead and add the relevant tasks to pull this effort off. |
Just pointing out that our WebTransport will be marked as "experimental" at first. This means that we won't make any guarantees regarding backwards-compatibility as the IETF draft evolves towards RFC status. If the changes between two draft versions are too large (and too cumbersome to support at the same time), we might decide to drop support for the older version. |
The last remaining open item for this issue was " initial interop with js-libp2p (manual testing is ok for now)" which is accomplished by this demo: Therefore, I am closing this issue. |
Done Criteria
WebTransport is another full-functioning transport in go-libp2p.
Two go-libp2p nodes can establish a connection using WebTransport following the spec.
The implementation is unit tested.
We have interoperability tests between versions.
libp2p documentation is updated for discoverability of this functionality
Why Important
This is covered more in the spec, but WebTransport provides a performant way for browsers (Chromium currently) to connect with the rest of the libp2p network.
Tasks
Notes
The text was updated successfully, but these errors were encountered: