Randy Reddig

> Wouldn’t it make more sense then to put this information in the http3.Conn? The `http3` package needs to know if the underlying `quic.Session` is a server or client. Currently...

How do you mean?

> Could this be refactored such that the `http3.Conn` is initialized close to where `quic.Listen` and `quic.Accept` is called? #3256 implements `http3.Accept(quic.EarlyStream, Settings)` for servers and `http3.Open(quic.EarlyStream, Settings)` for clients,...

This is a more recently-updated proposal to add unreliable datagrams to QUIC: https://github.com/tfpauly/draft-pauly-quic-datagram

> These changes mostly look fine to me on first sight, but I'm not sure I understand the motivation of this PR. Why do you want to export the `Settings`...

Here's my WIP branch that implements http3.Conn as a foundation to (de)multiplex datagrams and eventually WT streams: https://github.com/alta/quic-go/blob/http3/conn/http3/conn.go Edit: and yes, I agree that DATAGRAM is essential enough to implement...

I’ve made some progress adding WebTransport support to quic-go: https://github.com/lucas-clemente/quic-go/compare/master...alta:webtransport?expand=1 Progress so far: - Added support for `WEBTRANSPORT_ENABLED` H3 setting in client and server. - Defined WebTransport stream types. -...

> @ydnar Is this implementing the current draft of the WebTransport spec? > That's super exciting. Are you planning to send us a PR with your changes? Yep! I’m working...

> > current Chromium demo. I’d love your guidance on how best to test this. > > That might be a bit tricky. The ideal test would be running a...

Got first bytes echoed over a bidi WebTransport stream using Chrome: The handler looks like this: ```go func handleCounter(rw http.ResponseWriter, req *http.Request) { // TODO: check Origin header and ensure...