Changing net.Conn for a Connection about quic-go HOT 3 CLOSED

If I understand correctly, what you're referring to is QUIC Connection Migration. Unfortunately, it's a little bit more complicated than switching out the underlying net.PacketConn, as you 1. need to validate that the new path actually works and 2. need to deal with a path that might have vastly different parameters in terms of RTT and bandwidth.

See #234 and #3990 for more details.

from quic-go.

Thanks for the quick reply! Yes, I believe Connection Migration would be the correct terminology for what I intend to accomplish. I'm working on research applications using QUIC-go in a controlled environment; as such, I can guarantee in my setting that the new path does work and that the new path can use the same (or any arbitrary) initial parameters for RTT and bandwidth (which I assume contributes mainly to congestion control). With these controls in place, is it possible to plug in a different net.PacketConn with the current API?

from quic-go.

net.PacketConn is an interface, so you can write your own implementation that switches from one connection to the other, without any API changes in quic-go. Unfortunately, this will disable a number of optimizations that only work on actual UDP connections though (ECN and GSO, for example), which are pretty crucial if you're aiming for high throughput.

from quic-go.