search

BiagioFesta / wtransport

Async-friendly WebTransport implementation in Rust
Apache License 2.0
402 stars 27 forks source link

Update the timeout for a specific client/SocketAddr at runtime #184

Closed cBournhonesque closed 4 months ago

cBournhonesque commented 4 months ago

I have a case where some clients stop sending packets because they are running in a browser tab that has been throttled. I believe this could cause the webtransport connection to timeout.

I'm wondering if it's possible to update the timeout for an 'idle connection', as described in https://github.com/w3c/p2p-webtransport/issues/106

BiagioFesta commented 4 months ago

Are you referring Config::max_idle_timeout & Config::keep_alive_interval?

cBournhonesque commented 4 months ago

Yes.

I actually found another solution for my problem; but out of curiosity is it possible to update those settings even after the connection has been established?

BiagioFesta commented 4 months ago

but out of curiosity is it possible to update those settings even after the connection has been established?

No, it is not.

The underlying QUIC transport does not allow that. For example, max_idle_timeout is a QUIC transport parameters which is exchanged during connection establishment

cBournhonesque commented 4 months ago

Thank you!