Cleanup usage of JingleThread in the protocol code.

JingleThread was used in some places where it is not
necessary. Replace it with MessageLoop.

BUG=None
TEST=None

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

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

1 files changed, 2 insertions, 2 deletions

diff --git a/remoting/host/chromoting_host.cc b/remoting/host/chromoting_host.cc
index 0ebff52..ec9e8a2 100644
--- a/remoting/host/chromoting_host.cc
+++ b/remoting/host/chromoting_host.cc
@@ -117,7 +117,7 @@ void ChromotingHost::Start() {
       new XmppSignalStrategy(context_->jingle_thread(), xmpp_login,
                              xmpp_auth_token,
                              xmpp_auth_service));
-  jingle_client_ = new JingleClient(context_->jingle_thread(),
+  jingle_client_ = new JingleClient(context_->network_message_loop(),
                                     signal_strategy_.get(),
                                     NULL, NULL, NULL, this);
   jingle_client_->Init();
@@ -236,7 +236,7 @@ void ChromotingHost::OnStateChange(JingleClient* jingle_client,
 
     // Create and start session manager.
     protocol::JingleSessionManager* server =
-        new protocol::JingleSessionManager(context_->jingle_thread());
+        new protocol::JingleSessionManager(context_->network_message_loop());
     // TODO(ajwong): Make this a command switch when we're more stable.
     server->set_allow_local_ips(true);