1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
// Copyright (c) 2009 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.
// This header is meant to be included in multiple passes, hence no traditional
// header guard.
// See ipc_message_macros.h for explanation of the macros and passes.
// Developer tools consist of the following parts:
//
// DevToolsAgent lives in the renderer of an inspected page and provides access
// to the pages resources, DOM, v8 etc. by means of IPC messages.
//
// DevToolsClient is a thin delegate that lives in the tools front-end
// renderer and converts IPC messages to frontend method calls and allows the
// frontend to send messages to the DevToolsAgent.
//
// All the messages are routed through browser process. There is a
// DevToolsManager living in the browser process that is responsible for
// routing logistics. It is also capable of sending direct messages to the
// agent rather than forwarding messages between agents and clients only.
//
// Chain of communication between the components may be described by the
// following diagram:
// ----------------------------
// | (tools frontend |
// | renderer process) |
// | | --------------------
// |tools <--> DevToolsClient+<-- IPC -->+ (browser process) |
// |frontend | | |
// ---------------------------- ---------+----------
// ^
// |
// IPC
// |
// v
// --------------------------+--------
// | inspected page <--> DevToolsAgent |
// | |
// | (inspected page renderer process) |
// -----------------------------------
//
// This file describes developer tools message types.
#include "ipc/ipc_message_macros.h"
// These are messages sent from DevToolsAgent to DevToolsClient through the
// browser.
IPC_BEGIN_MESSAGES(DevToolsClient)
// Sends glue-level Rpc message to the client.
IPC_MESSAGE_CONTROL5(DevToolsClientMsg_RpcMessage,
std::string /* class_name */,
std::string /* method_name */,
std::string /* p1 */,
std::string /* p2 */,
std::string /* p3 */)
IPC_END_MESSAGES(DevToolsClient)
//-----------------------------------------------------------------------------
// These are messages sent from DevToolsClient to DevToolsAgent through the
// browser.
IPC_BEGIN_MESSAGES(DevToolsAgent)
// Tells agent that there is a client host connected to it.
IPC_MESSAGE_CONTROL0(DevToolsAgentMsg_Attach)
// Tells agent that there is no longer a client host connected to it.
IPC_MESSAGE_CONTROL0(DevToolsAgentMsg_Detach)
// Sends glue-level Rpc message to the agent.
IPC_MESSAGE_CONTROL5(DevToolsAgentMsg_RpcMessage,
std::string /* class_name */,
std::string /* method_name */,
std::string /* p1 */,
std::string /* p2 */,
std::string /* p3 */)
// Send debugger command to the debugger agent. Debugger commands should
// be handled on IO thread(while all other devtools messages are handled in
// the render thread) to allow executing the commands when v8 is on a
// breakpoint.
IPC_MESSAGE_CONTROL1(DevToolsAgentMsg_DebuggerCommand,
std::string /* command */)
// Inspect element with the given coordinates.
IPC_MESSAGE_CONTROL2(DevToolsAgentMsg_InspectElement,
int /* x */,
int /* y */)
IPC_END_MESSAGES(DevToolsAgent)
|
