Switch IPC::ChannelProxy to use MessageLoopProxy instead of MessageLoop. This allows us to remov...

chrome/renderer/devtools_agent_filter.h

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_RENDERER_DEVTOOLS_AGENT_FILTER_H_
 #define CHROME_RENDERER_DEVTOOLS_AGENT_FILTER_H_
 #pragma once
 
 #include <string>
 
 #include "ipc/ipc_channel_proxy.h"
 
+class MessageLoop;
 struct DevToolsMessageData;
 
 // DevToolsAgentFilter is registered as an IPC filter in order to be able to
 // dispatch messages while on the IO thread. The reason for that is that while
 // debugging, Render thread is being held by the v8 and hence no messages
 // are being dispatched there. While holding the thread in a tight loop,
 // v8 provides thread-safe Api for controlling debugger. In our case v8's Api
 // is being used from this communication agent on the IO thread.
 class DevToolsAgentFilter : public IPC::ChannelProxy::MessageFilter {
  public:
@@ skipping 21 matching lines @@
 
   // Made static to allow DevToolsAgent to use it for replying directly
   // from IO thread.
   static int current_routing_id_;
   static IPC::Channel* channel_;
 
   DISALLOW_COPY_AND_ASSIGN(DevToolsAgentFilter);
 };
 
 #endif  // CHROME_RENDERER_DEVTOOLS_AGENT_FILTER_H_