Skip to content
WebTransport is a web API for flexible data transport
Branch: master
Clone or download
pthatcherg Merge pull request #16 from WICG/whatwg-streams
Update the explainer to use WHATWG streams
Latest commit 429dce8 Jul 11, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
include Set the WG name to WICG Jul 9, 2019
CODE_OF_CONDUCT.md Adding baseline CODE_OF_CONDUCT.md May 29, 2019
CONTRIBUTING.md Adding baseline CONTRIBUTING.md May 29, 2019
LICENSE.md Adding baseline LICENSE.md May 29, 2019
README.md
explainer.md Don't use .ready incorrectly, and add a note to the README about the … Jul 11, 2019
index.html Expand Security Considerations section Jun 21, 2019
w3c.json Adding baseline w3c.json May 29, 2019

README.md

WebTransport

API that allows web applications to establish interactive, bidirectional, multiplexed network connections

It fills gaps in the web platform:

  • Lack of UDP-like networking API
  • Lack of WebSocket-like API without head-of-line blocking

It provides:

  • Reliable streams
  • Unreliable datagrams
  • Encryption and congestion control
  • An origin-based security model
  • Bindings for QUIC
  • Multiplexing with existing HTTP/3 connections
  • Flexible API that can be extended to other protocols, such as TCP fallback and p2p
  • Ability to change transport without changing application code

It's great for:

  • sending or receiving high-frequency, small messages that don't need to be reliable (like game state)
  • sending or receiving low-latency media
  • transferring files

See the explainer for more info.

See the proposed spec.

Note that the proposed spec is out of date compared to the explainer because new ideas are first developed in the explainer before the spec. In particular, at this time the explainer uses ReadableStreams and WritableStreams (aka WHATWG streams) and the spec does not.

You can’t perform that action at this time.