Use MessageLoopProxy for network message loop.

Use MessageLoopProxy for network message loop.

When we switch to P2P Pepper API we will need to run networking code on the 
main plugin thread. Switching to MessageLoopProxy for network thread, so that 
it's easier to switch network thread in the future.

BUG=None
TEST=None

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

[Wez, 2011-08-12 21:11:20]

If I understand this CL correctly, you're adding a |network_message_loop|
parameter to the top-level connection classes, for them to be able to pass to
the BufferedSocketWriter and similar classes that perform the thread-hopping. 
Is that correct?

http://codereview.chromium.org/7633009/diff/4001/remoting/client/client_conte...
File remoting/client/client_context.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/client/client_conte...
remoting/client/client_context.cc:41: &InitializeMessageLoopProxy,
&network_message_loop_, &proxy_event));
Is there a reason we can't just call message_loop_proxy() on |network_thread_|
here?

http://codereview.chromium.org/7633009/diff/4001/remoting/host/chromoting_hos...
File remoting/host/chromoting_host_context.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/host/chromoting_hos...
remoting/host/chromoting_host_context.cc:45: proxy_event.Wait();
Again, use message_loop_proxy() here?

http://codereview.chromium.org/7633009/diff/4001/remoting/protocol/protocol_t...
File remoting/protocol/protocol_test_client.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/protocol/protocol_t...
remoting/protocol/protocol_test_client.cc:236: proxy_event.Wait();
Thread::message_loop_proxy() again.

[Sergey Ulanov, 2011-08-12 21:24:00]

On 2011/08/12 21:11:20, Wez wrote:
> If I understand this CL correctly, you're adding a |network_message_loop|
> parameter to the top-level connection classes, for them to be able to pass to
> the BufferedSocketWriter and similar classes that perform the thread-hopping. 
> Is that correct?
Yes, network code will run on plugin thread, so we cannot use MessageLoop for
the network thread.

[Sergey Ulanov, 2011-08-12 21:24:17]

http://codereview.chromium.org/7633009/diff/4001/remoting/client/client_conte...
File remoting/client/client_context.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/client/client_conte...
remoting/client/client_context.cc:41: &InitializeMessageLoopProxy,
&network_message_loop_, &proxy_event));
On 2011/08/12 21:11:20, Wez wrote:
> Is there a reason we can't just call message_loop_proxy() on |network_thread_|
> here?
I didn't know about Thread::message_loop_proxy(). WIll fix it. Thanks!

http://codereview.chromium.org/7633009/diff/4001/remoting/host/chromoting_hos...
File remoting/host/chromoting_host_context.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/host/chromoting_hos...
remoting/host/chromoting_host_context.cc:45: proxy_event.Wait();
On 2011/08/12 21:11:20, Wez wrote:
> Again, use message_loop_proxy() here?
Added message_loop_proxy() in JingleThread.

http://codereview.chromium.org/7633009/diff/4001/remoting/protocol/protocol_t...
File remoting/protocol/protocol_test_client.cc (right):

http://codereview.chromium.org/7633009/diff/4001/remoting/protocol/protocol_t...
remoting/protocol/protocol_test_client.cc:236: proxy_event.Wait();
On 2011/08/12 21:11:20, Wez wrote:
> Thread::message_loop_proxy() again.

Done.

[Wez, 2011-08-12 21:44:54]

LGTM with the message_loop_proxy() change.