Don't depend on MessageLoopProxy in remoting protocol code.

Don't depend on MessageLoopProxy in remoting protocol code.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=138731

[Sergey Ulanov, 2012-05-23 00:09:26]

I'm going to remove most references to MessageLoopProxy in chromoting code
because MessageLoopProxy::current() doesn't work on plugin threads. Instead
ThreadTaskRunnerHandle and SingleThreadTaskRunner should be used. This is a
first patch in the series.

[Alpha Left Google, 2012-05-23 20:31:36]

On 2012/05/23 00:09:26, sergeyu wrote:
> I'm going to remove most references to MessageLoopProxy in chromoting code
> because MessageLoopProxy::current() doesn't work on plugin threads. Instead
> ThreadTaskRunnerHandle and SingleThreadTaskRunner should be used. This is a
> first patch in the series.

LGTM.

[commit-bot: I haz the power, 2012-05-24 01:31:28]

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

[commit-bot: I haz the power, 2012-05-24 04:15:55]

Change committed as 138731