Results 34 comments of Robin Thellend

For http/1, http/2, and the other TCP based connections, all the accounting is done on the incoming `net.Conn`. That's actually easier. For the QUIC connections, the accounting is done on...

My solution for now is to generate a set of interfaces and wrapper structs that look a lot like the old API. This is pretty straight forward using reflection. https://pkg.go.dev/github.com/c2FmZQ/[email protected]/api...

I split the quic-go-api repo into two, and made them compatible with mainline quic-go. https://pkg.go.dev/github.com/c2FmZQ/quic-api https://pkg.go.dev/github.com/c2FmZQ/http3-go quic-api contains the auto-generated interfaces and wrappers that look a lot like the pre-v0.53...

After https://github.com/quic-go/quic-go/pull/5256, creating a new http3 repo should be pretty straight forward: ```bash git clone https://github.com/quic-go/quic-go.git cd quic-go/ git filter-repo --subdirectory-filter http3 cp /quic-go/{LICENSE,SECURITY.md} . sed -i -re 's:github.com/quic-go/quic-go/http3:github.com/quic-go/http3-go:g' server_test.go...