You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it takes a long time to detect networking issues. It may even take longer to detect the networking issue than it does to resolve it. Some ways to fix this are either:
use if-watch to kill connections as soon as the interface going down was detected
ping more frequently
there are some caveats with these options:
seems pretty unreliable as we need to track what interface the connection comes from.
should work well. but to avoid spaming the network with ping messages it would be nice if there was the ability to send pings only if the connection was idle
The text was updated successfully, but these errors were encountered:
Hmm, we could implement a final callback on ProtocolsHandler that gets called if we are planning to shutdown.
An alternative would be to refactor away the automatic closing of connections and instead only report to the behaviour that all handlers for a connection are idle. The behaviour could then choose to either send a message or close the connection.
I don't think this will be required for quic as quic already has a built in keep alive mechansim. tcp kind of has something but it apparently doesn't always work as one would expect.
Currently it takes a long time to detect networking issues. It may even take longer to detect the networking issue than it does to resolve it. Some ways to fix this are either:
there are some caveats with these options:
The text was updated successfully, but these errors were encountered: