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
If a publisher notices an increase of subscriber packet acknowledgement timeouts, leading to TCP-based resends, then this shall be taken as an indication of network congestion.
At that point we shall stop sending any traffic via UDP multicast for a given number of microseconds, forcing sends to be done via the flow control-supporting TCP channel.
If the publisher, once the multicast traffic resumes, immediately detects congestion again, it shall back off for the double period of time. With this solution we get an exponential back-off, allowing us to rely on TCP to throttle IP traffic and deliver packets via congested networks.
The text was updated successfully, but these errors were encountered:
If a publisher notices an increase of subscriber packet acknowledgement timeouts, leading to TCP-based resends, then this shall be taken as an indication of network congestion.
At that point we shall stop sending any traffic via UDP multicast for a given number of microseconds, forcing sends to be done via the flow control-supporting TCP channel.
If the publisher, once the multicast traffic resumes, immediately detects congestion again, it shall back off for the double period of time. With this solution we get an exponential back-off, allowing us to rely on TCP to throttle IP traffic and deliver packets via congested networks.
The text was updated successfully, but these errors were encountered: