Consortium w3c introduced the first draft specification Webtransport that defines the protocol and related JavaScript API to send and receive data between the browser and the server. The communication channel is organized on top of HTTP / 3 using the Quic protocol as transport, which, in turn, is an add-in above the UDP protocol that supports multiplexing multiple compounds and providing encryption methods equivalent to TLS / SSL.
WebTransport can be used instead of the WebSockets mechanism, offering such additional features as the transfer of transmission to several streams, unidirectional flows, delivery without taking into account the order of sending packages (Out-of-Order), reliable and unreliable delivery modes. In addition, WebTransport can be applied instead of the Server Push mechanism, from which Google refused to Chrome.