[DevTools] Rework DevToolsSession interaction with domain handlers.

content/browser/devtools/protocol/devtools_domain_handler.h

Index: content/browser/devtools/protocol/devtools_domain_handler.h
diff --git a/content/browser/devtools/protocol/devtools_domain_handler.h b/content/browser/devtools/protocol/devtools_domain_handler.h
new file mode 100644
index 0000000000000000000000000000000000000000..6eb27b569349c8f68a050d7db38ff3cfb8ca52d1
--- /dev/null
+++ b/content/browser/devtools/protocol/devtools_domain_handler.h
@@ -0,0 +1,36 @@
+// Copyright 2016 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 CONTENT_BROWSER_DEVTOOLS_PROTOCOL_DEVTOOLS_DOMAIN_HANDLER_H_
+#define CONTENT_BROWSER_DEVTOOLS_PROTOCOL_DEVTOOLS_DOMAIN_HANDLER_H_
+
+#include "content/browser/devtools/protocol/forward.h"
+
+namespace content {
+
+class RenderFrameHostImpl;
+
+namespace protocol {
+
+class DevToolsDomainHandler {
+ public:
+  explicit DevToolsDomainHandler(const std::string& name);
+  virtual ~DevToolsDomainHandler();
+
+  virtual void SetRenderFrameHost(RenderFrameHostImpl* host);
+  virtual void Wire(UberDispatcher* dispatcher);
+  virtual Response Disable();

[caseq, 2016/12/20 23:13:20]

I wonder if we can get rid of that. This is not the protocol method, so why
would it return Response? Should we just generate a generic protocol wrapper
around that?

[dgozman, 2016/12/21 00:29:40]

Per offline discussion: we didn't find a clear solution which is definitely a
win over this.

+
+  const std::string& name() const { return name_; }
+
+ private:
+  std::string name_;
+
+  DISALLOW_COPY_AND_ASSIGN(DevToolsDomainHandler);
+};
+
+}  // namespace protocol
+}  // namespace content
+
+#endif  // CONTENT_BROWSER_DEVTOOLS_PROTOCOL_DEVTOOLS_DOMAIN_HANDLER_H_