![]() ![]() We will use a linked client example to connect to a server that runs on localhost and uses /lucas-clemente/quic-go library. ![]() You should not use it in production yet.Įxperimenting with QuicTransport post contains links to a client example and companion Python server implementation. WebTransport drafts, Quic-Go library, even QUIC protocol itself are subjects to change. Please keep in mind that all things described in this post are work in progress. Developers can initialize transport with code like this: WebTransport over HTTP/3 – this spec describes HTTP/3-based transport for WebTransport (actually HTTP/3 is a protocol defined on top of QUIC)Īt moment Chrome only implements trial possibility to try out WebTransport standard and only implements WebTransport over QUIC.WebTransport over QUIC – this spec describes QUIC-based transport for WebTransport.WebTransport overview – this spec gives an overview of WebTransport and provides requirements to transport layer.To help you figure out things here are links to current WebTransport specs: This is sweet for in-browser real-time games. WebTransport also defines an unreliable stream API using UDP datagrams (which is possible since QUIC is UDP-based) – which is what browsers did not have before without a rather complex WebRTC setup involving ICE, STUN, etc.It can be a good alternative to WebSocket messaging, standard provides some capabilities that are not possible with current WebSocket spec: possibility to get rid of head-of-line blocking problems using individual streams for different data, the possibility to reuse a single connection to a server in different browser tabs.WebTransport standard will provide a possibility to use streaming client-server communication using modern transports such as QUIC and HTTP/3. ![]() Here we will concentrate on implementing server side. If you have not heard about it before I suggest to first read a post called Experimenting with QuicTransport published recently on web.dev – it gives a nice overview to WebTransport and shows client-side code examples. WebTransport is a new browser API offering low-latency, bidirectional, client-server messaging. Maybe we will publish a follow-up of this post at some point. For example the working group has no plan to implement both QuicTransport and HTTP3-based transports – only HTTP3 based WebTransport is going to be implemented. Most information here is not actual anymore. UPDATE: WebTransport spec is still evolving. ![]()
0 Comments
Leave a Reply. |