Make reconnection in response to video channel inactivity less aggressive.

Make reconnection in response to video channel inactivity less aggressive.

Previously immediate reconnection was triggered by the video channel
becoming inactive. That can cause spurious reconnects on flaky networks.
Now the webapp will always wait for 10 seconds before trying to reconnect.

BUG=375568
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=272695

[Jamie, 2014-05-23 20:21:16]

lgtm

[Wez, 2014-05-23 20:26:39]

lgtm

https://codereview.chromium.org/297963005/diff/20001/remoting/webapp/smart_re...
File remoting/webapp/smart_reconnector.js (left):

https://codereview.chromium.org/297963005/diff/20001/remoting/webapp/smart_re...
remoting/webapp/smart_reconnector.js:110: if (navigator.onLine) {
Would it be better to just have a shorter timeout for the am-online case, before
reconnecting?  Or is navigator.onLine just too unreliable for our purposes?

[Sergey Ulanov, 2014-05-23 20:38:35]

https://codereview.chromium.org/297963005/diff/20001/remoting/webapp/smart_re...
File remoting/webapp/smart_reconnector.js (left):

https://codereview.chromium.org/297963005/diff/20001/remoting/webapp/smart_re...
remoting/webapp/smart_reconnector.js:110: if (navigator.onLine) {
On 2014/05/23 20:26:40, Wez wrote:
> Would it be better to just have a shorter timeout for the am-online case,
before
> reconnecting?  Or is navigator.onLine just too unreliable for our purposes?

navigator.onLine=true just tells us that the machine might be online. It's still
possible that network is broken. So I don't think we should treat that case
differently.

[Sergey Ulanov, 2014-05-23 20:38:40]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-05-23 20:39:56]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/297963005/20001

[commit-bot: I haz the power, 2014-05-24 03:13:14]

Change committed as 272695