Change reconnect timer delay to 2 seconds instead of 1

Change video channel timeout to 2 seconds instead of 1

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

[Wez, 2014-05-23 01:05:48]

What's this number based upon?

With the current timeout I observe sessions to basically responsive hosts
regularly becoming greyed out and unresponsive; is two seconds sufficiently much
longer to avoid these transient delays being escalated into grey-outs or
disconnects?

[Sergey Ulanov, 2014-05-23 19:33:52]

On 2014/05/23 01:05:48, Wez wrote:
> What's this number based upon?
> 
> With the current timeout I observe sessions to basically responsive hosts
> regularly becoming greyed out and unresponsive; is two seconds sufficiently
much
> longer to avoid these transient delays being escalated into grey-outs or
> disconnects?

The logic here is that if connection is inactive for 2 seconds it's not usable,
so we want to gray it out. 1 second is too aggressive. MonitoredVideoStub
doesn't reconnect connection itself. It just tells the webapp that video channel
is not active. When video channel becomes inactive the webapp may reconnect
immediately. See
https://code.google.com/p/chromium/codesearch#chromium/src/remoting/webapp/sm...
. Currently it checks if the client is online and reconnects immediately only
when it's online, otherwise it waits for 10 seconds. I'm not sure that's the
right solution - it will cause spurious reconnects on a flaky network, but it's
separate from this change. This change should prevent the screen from being
grayed out too often on a slower networks.

[Wez, 2014-05-24 05:25:44]

lgtm

[commit-bot: I haz the power, 2014-05-24 05:26:32]

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

[commit-bot: I haz the power, 2014-05-24 07:01:58]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[commit-bot: I haz the power, 2014-05-24 07:26:56]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-24 07:26:56]

Try jobs failed on following builders:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[Sergey Ulanov, 2014-05-24 09:01:56]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-05-24 09:02:45]

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

[commit-bot: I haz the power, 2014-05-24 09:10:17]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[commit-bot: I haz the power, 2014-05-24 09:18:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-24 09:18:12]

Try jobs failed on following builders:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[Sergey Ulanov, 2014-05-25 06:30:42]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-05-25 06:30:49]

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

[commit-bot: I haz the power, 2014-05-25 06:35:55]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[commit-bot: I haz the power, 2014-05-25 06:41:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-25 06:41:51]

Try jobs failed on following builders:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[Sergey Ulanov, 2014-05-25 07:32:50]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-05-25 07:33:15]

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

[commit-bot: I haz the power, 2014-05-25 07:39:07]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/7...)

[commit-bot: I haz the power, 2014-05-26 04:28:34]

Change committed as 272788