You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libp2p maintainers have specified and are adding support for the Browser to Server aspect of the WebRTC transport protocol across three implementations:
Per the working draft, three libp2p implementations are estimated to add support by end of Q4 2022 (go-libp2p, js-libp2p, and rust-libp2p) (✅ rust-libp2p has been merged)
Documentation for "WebRTC: Browser to Server" exists under the "Transports" section
describes WebRTC in general
describes WebRTC Browser to Server in libp2p
compare/contrast with what WebRTC offers vs other supported transports
acknowledges WebRTC Browser to Browser is not yet fully specified/implemented
Why Important
Expanding the ways libp2p enables connectivity (beyond standalone nodes and into browser connectivity) is a primary goal of the libp2p project, WebRTC is center to that.
As we finish specification and implementation, we need corresponding documentation for the transport and it's use-cases.
libp2p maintainers have specified and are adding support for the Browser to Server aspect of the WebRTC transport protocol across three implementations:
Working Draft
version of the specification is merged: webrtc/: Add libp2p WebRTC browser-to-server spec specs#412Done Criteria
Why Important
Expanding the ways libp2p enables connectivity (beyond standalone nodes and into browser connectivity) is a primary goal of the libp2p project, WebRTC is center to that.
As we finish specification and implementation, we need corresponding documentation for the transport and it's use-cases.
Related
The text was updated successfully, but these errors were encountered: