Moving to WebTransport

Question

Moving to WebTransport

Closed this issue 3 years ago · 5 comments

jianjunz commented 3 years ago

quic-transport will no longer be supported by browser. Moving to HTTP/3 based WebTransport to align with spec.

Answer 1 · 2021-06-19T22:24:02.000Z

Can we use this as server code for HTTP/3 over WebTransport? Are there any examples? See GoogleChrome/samples#718.

Answer 2 · 2021-06-20T15:47:15.000Z

Implementation of HTTP/3 over WebTransport is still working in progress. Please see #29 for its latest status. Thanks.

Answer 3 · 2021-06-20T15:51:33.000Z

What are you using now?

Does this repository currently use the deprecated/removed quic-transport isolated from Chromium source code?

I was using QuicTransport/quic-transport https://github.com/guest271314/quictransport prior to deprecation and am curious if the Chromium source code can be farmed out to its own module so that the code can still be used?

Answer 4 · 2021-06-21T01:22:16.000Z

This repository currently uses quic-transport.

Public APIs provided by this SDK doesn't involve Chromium's header files, but the implementation is based on Chromium source code. So developers of this repository need to pull Chromium source code for compiling, while users don't.

Answer 5 · 2021-07-27T01:09:55.000Z

Main branch is moved to WebTransport over HTTP/3.