Jesse Wilson

Calling flush after committing an edit would work.

I'd prefer to not reuse the instance by default. We don't reuse it that in OkHttp’s test suite and it's never been a performance problem.

No way to manipulate this currently. I'm not even sure where we'd add that configuration option in our API.

That's the most obvious option. The drawback is that the request that creates the tunnel is arbitrary. If you have a connection that carries multiple requests, they may each use...

Yikes, yes this is definitely OkHttp's fault. Thanks for the careful test case, that'll make this easier to fix!

Yup. Though it isn't a high priority yet!

Yup! We're still waiting on some sort of **stable** QUIC spec.

@bgcr please do your work in a fork! We don't have time or interest to have QUIC in trunk at this time.

https://www.ietf.org/proceedings/96/slides/slides-96-quic-5.pdf

We make no API compatibility promises for our `internal` packages. So those changes aren’t precluded. In Connection we may need to hack a few things to keep a consistent API,...