Re: [w3ctag/design-reviews] WebTransport review request (#669)

Sure thing, and thanks. Major changes since July 2020:
 1. The spec is now in the W3C, not WICG
 2. Removed the multiple-transport abstraction. HTTP/3 is now the sole transport, simplifying the model significantly
    - We're still working on implicit HTTP/2 https://github.com/w3c/webtransport/issues/107 where HTTP/3 is unavailable
 3. Integrates with the fetch spec to [obtain a connection](https://fetch.spec.whatwg.org/#concept-connection-obtain); may be [pooled](https://w3c.github.io/webtransport/#dom-webtransportoptions-allowpooling) but this has no implementations yet; JS gets a dedicated server connection by default
 4. Connection URLs now use the “https" scheme, and must include the port
 4. SecureContext only, exposed on Window and DedicatedWorker
 6. WHATWG streams are used throughout, even for datagrams (where they provide [local back-pressure sender-side](https://docs.google.com/presentation/d/1SG1FUvn9UKGx_gAqWnCzPHlsIXkDUXctZPs7blfqS5k/edit?pli=1#slide=id.gf66ea8b320_2_56))
 7. Fleshed out streams algorithms with underlying queues, back pressure, and error handling 
 8. Removed custom network (QUIC) abort APIs and integrated with WHATWG stream abort semantics instead:
     ```js
    stream.abort(new WebTransportError({streamErrorCode})) // aborts stream with same code on client & server
    ````
 9. Operates on [BufferSource](https://webidl.spec.whatwg.org/#BufferSource) data, with (streams) semantics lower-level than WebSocket (message) semantics:
    - Use single stream for data you need to arrive in order (but [BYO framing](https://docs.google.com/presentation/d/1SG1FUvn9UKGx_gAqWnCzPHlsIXkDUXctZPs7blfqS5k/edit?pli=1#slide=id.gf738c3f75d_9_71))
    - Use separate streams for data that should arrive in parallel but can arrive out of order
 10. Close code from server (not an error): `const {closeCode, reason} = await wt.closed`
 11. CSP

Unfortunately, the explainer is a bit outdated. I hope to get to that soon in https://github.com/w3c/webtransport/issues/319.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/669#issuecomment-972383932