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

Review URL: http://codereview.chromium.org/7633009

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96651 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 6 insertions, 1 deletions

diff --git a/remoting/protocol/video_writer.h b/remoting/protocol/video_writer.h
index 68b19fd..2b5a7be 100644
--- a/remoting/protocol/video_writer.h
+++ b/remoting/protocol/video_writer.h
@@ -14,6 +14,10 @@
 #include "base/callback.h"
 #include "remoting/protocol/video_stub.h"
 
+namespace base {
+class MessageLoopProxy;
+}  // namespace base
+
 namespace remoting {
 namespace protocol {
 
@@ -28,7 +32,8 @@ class VideoWriter : public VideoStub {
   // parameter is set to true on success.
   typedef base::Callback<void(bool)> InitializedCallback;
 
-  static VideoWriter* Create(const SessionConfig* config);
+  static VideoWriter* Create(base::MessageLoopProxy* message_loop,
+                             const SessionConfig* config);
 
   // Initializes the writer.
   virtual void Init(Session* session, const InitializedCallback& callback) = 0;