[Cast Channel] Implement random backoff on disovery |
||
Issue descriptionIf a Cast device comes online on a network with many Chrome browsers, they may all attempt to connect at once. Older devices have a limited ability to handle signing operations and this will freeze the device until all connections are completed (or time out). To help prevent a connection flood we can implement a random wait after discovery for the initial connection, along with exponential backoff plus some random value for retries.
,
Oct 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/81fdeeec321b6d25364d76a71ed59951f15a2295 commit 81fdeeec321b6d25364d76a71ed59951f15a2295 Author: Bin Zhao <zhaobin@chromium.org> Date: Fri Oct 20 22:28:39 2017 [Media Router] Add a random delay before opening cast channels in CastMediaSinkService When a device comes online, multiple Chrome instances may connect to the same device at the same time. Added a random delay before 0 - 5 seconds before opening cast channels to prevent this. Bug: 770357 Change-Id: I237a3b9539b3dc3df08477e7f31895300f3539ec Reviewed-on: https://chromium-review.googlesource.com/719467 Commit-Queue: Bin Zhao <zhaobin@chromium.org> Reviewed-by: mark a. foltz <mfoltz@chromium.org> Reviewed-by: Derek Cheng <imcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#510584} [modify] https://crrev.com/81fdeeec321b6d25364d76a71ed59951f15a2295/chrome/browser/media/router/discovery/mdns/cast_media_sink_service.cc
,
Oct 23 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by sko...@chromium.org
, Oct 9 2017