Benjamin Saunders

My reading of that text is that the reason phrase and code must be cleared *in cases where we would normally send a 0x1d frame*. In this case we're explicitly...

Also affecting me. Going to have to downgrade for now... 0.6.62 indeed does not have the issue.

The idle timeout can't be reliably changed on an existing connection because it's part of the transport parameters sent to the peer, the peer is responsible for respecting the value...

If you need to register for wakeups, create and poll a future using the existing APIs you've already identified. You can't register to be woken without a future, because that's...

You can easily implement `readable`/`try_recv` today: ```rs struct MyTransport { connection: quinn::Connection, recv_buffer: Option, } impl DatagramTransport for MyTransport { async fn readable(&self) -> io::Result { if self.recv_buffer.is_some() { return...

> If you’d be open to also accepting the readable plus try_recv It's not clear to me that these add anything. > but I wouldn’t want to rely on it....

Closing as the questions here seem to be fully addressed.

I actually don't think this is surprising. The direction in the reverse of most application data flow will consist mostly of ACKs. When an ACK is lost, recovery of the...

To be clear, Quinn's BBR congestion controller isn't really maintained, and I'm not sure anyone has the resources to investigate its behavior. If Cubic works for you I'd encourage you...

It's a very cool concept, and we'd love to support it properly, but there are presently no contributors with the time to drive it forwards. Bear in mind that even...