The W3C Consortium has presented the first draft of the WebTransport specification, defining the protocol and accompanying JavaScript API for sending and receiving data between the browser and the server. The communication channel is established over HTTP/3 using QUIC as the transport protocol, which, in turn, is a layer over UDP that supports multiplexing multiple connections and provides encryption methods equivalent to TLS/SSL.
WebTransport can be used instead of the WebSockets mechanism, offering additional features such as multi-stream transmission, unidirectional streams, out-of-order packet delivery, and both reliable and unreliable delivery modes. Additionally, WebTransport can be used instead of the Server Push mechanism, which Google has abandoned in Chrome.
Source: opennet.ru
