Use IpcVideoFrameCapturer on network thread instead of capturer thread.

Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from
ChromotingHost and ClientSession.

BUG=458437
Committed: https://crrev.com/85df3c48fd4a3be69b1a650cebc793024d4879b3
Cr-Commit-Position: refs/heads/master@{#375412}

[Sergey Ulanov, 2016-02-05 20:39:02]

Patchset #1 (id:1) has been deleted

[Sergey Ulanov, 2016-02-05 20:41:16]

Description was changed from

==========
Use IpcVideoFrameCapturer on network thread instead of capturer thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread.

BUG=458437
==========

to

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

BUG=458437
==========

[Sergey Ulanov, 2016-02-05 20:41:17]

sergeyu@chromium.org changed reviewers:
+ joedow@chromium.org

[Sergey Ulanov, 2016-02-05 21:01:52]

Description was changed from

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

BUG=458437
==========

to

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from 
ChromotingHost and ClientSession.

BUG=458437
==========

[Sergey Ulanov, 2016-02-05 21:02:04]

The CQ bit was checked by sergeyu@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-02-05 21:04:17]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1673723002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1673723002/60001

[joedow, 2016-02-05 21:39:26]

lgtm

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/ipc_deskt...
File remoting/host/ipc_desktop_environment.h (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/ipc_deskt...
remoting/host/ipc_desktop_environment.h:134: // events.
nit: Reword: Defines whether desktop environments created by this factory will
support touch events by default.

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
File remoting/host/me2me_desktop_environment.cc (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
remoting/host/me2me_desktop_environment.cc:68: // see http://crbug.com/73423.
It's save to enable it here because it works
s/save/safe

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
File remoting/host/me2me_desktop_environment.h (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
remoting/host/me2me_desktop_environment.h:84: bool curtain_enabled_;
In the other changes you moved the defaults for primitive types from the
initializer lists to the class definition, do you want to do that here as well? 
Not super important so feel free to skip for this CL.

[Sergey Ulanov, 2016-02-05 21:51:20]

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/ipc_deskt...
File remoting/host/ipc_desktop_environment.h (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/ipc_deskt...
remoting/host/ipc_desktop_environment.h:134: // events.
On 2016/02/05 21:39:26, joedow wrote:
> nit: Reword: Defines whether desktop environments created by this factory will
> support touch events by default.

Done. Note that this is no a new comment. I just reordered members because they
were in a wrong order.

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
File remoting/host/me2me_desktop_environment.cc (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
remoting/host/me2me_desktop_environment.cc:68: // see http://crbug.com/73423.
It's save to enable it here because it works
On 2016/02/05 21:39:26, joedow wrote:
> s/save/safe

Done.

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
File remoting/host/me2me_desktop_environment.h (right):

https://codereview.chromium.org/1673723002/diff/60001/remoting/host/me2me_des...
remoting/host/me2me_desktop_environment.h:84: bool curtain_enabled_;
On 2016/02/05 21:39:26, joedow wrote:
> In the other changes you moved the defaults for primitive types from the
> initializer lists to the class definition, do you want to do that here as
well? 
> Not super important so feel free to skip for this CL.

Done.

[Sergey Ulanov, 2016-02-05 21:51:26]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-02-05 21:51:26]

The patchset sent to the CQ was uploaded after l-g-t-m from joedow@chromium.org
Link to the patchset: https://codereview.chromium.org/1673723002/#ps80001
(title: " ")

[commit-bot: I haz the power, 2016-02-05 21:53:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1673723002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1673723002/80001

[commit-bot: I haz the power, 2016-02-05 22:25:26]

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

[commit-bot: I haz the power, 2016-02-05 22:25:27]

Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[Sergey Ulanov, 2016-02-13 01:31:54]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-02-13 01:31:54]

The patchset sent to the CQ was uploaded after l-g-t-m from joedow@chromium.org
Link to the patchset: https://codereview.chromium.org/1673723002/#ps160001
(title: " ")

[commit-bot: I haz the power, 2016-02-13 01:33:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1673723002/160001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1673723002/160001

[commit-bot: I haz the power, 2016-02-13 01:51:53]

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

[commit-bot: I haz the power, 2016-02-13 01:51:53]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[Sergey Ulanov, 2016-02-15 05:31:41]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-02-15 05:31:41]

The patchset sent to the CQ was uploaded after l-g-t-m from joedow@chromium.org
Link to the patchset: https://codereview.chromium.org/1673723002/#ps180001
(title: " ")

[commit-bot: I haz the power, 2016-02-15 05:33:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1673723002/180001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1673723002/180001

[commit-bot: I haz the power, 2016-02-15 05:59:15]

Description was changed from

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from 
ChromotingHost and ClientSession.

BUG=458437
==========

to

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from 
ChromotingHost and ClientSession.

BUG=458437
==========

[commit-bot: I haz the power, 2016-02-15 05:59:16]

Committed patchset #9 (id:180001)

[commit-bot: I haz the power, 2016-02-16 22:48:51]

Description was changed from

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from 
ChromotingHost and ClientSession.

BUG=458437
==========

to

==========
Use IpcVideoFrameCapturer on network thread instead of capture thread.

Previously IpcVideoFrameCapturer was called on the capturer thread,
while all IPC messages are sent and received on the network thread. Now
DesktopEnvironment implementations are responsible for creation of
DesktopCapturerProxy and MouseCursorMonitorProxy if necessary. This
allows to avoid capture thread on windows in the network process.

Also cleaned up unnecessary references to various task runners from
ChromotingHost and ClientSession.

BUG=458437

Committed: https://crrev.com/85df3c48fd4a3be69b1a650cebc793024d4879b3
Cr-Commit-Position: refs/heads/master@{#375412}
==========

[commit-bot: I haz the power, 2016-02-16 22:48:52]

Patchset 9 (id:??) landed as
https://crrev.com/85df3c48fd4a3be69b1a650cebc793024d4879b3
Cr-Commit-Position: refs/heads/master@{#375412}