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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
crateix!;
//-------------------------------------------[.cpp/bitcoin/src/ipc/protocol.h]
//-------------------------------------------[.cpp/bitcoin/src/interfaces/ipc.h]
/**
| IPC protocol interface for calling IPC methods
| over sockets.
|
| There may be different implementations of this
| interface for different IPC protocols
| (e.g. Cap'n Proto, gRPC, JSON-RPC, or custom
| protocols).
*/
/**
| IPC process interface for spawning bitcoin
| processes and serving requests in processes
| that have been spawned.
|
| There will be different implementations of
| this interface depending on the platform
| (e.g. unix, windows).
*/
/**
| Interface providing access to
| interprocess-communication (IPC)
| functionality. The IPC implementation is
| responsible for establishing connections
| between a controlling process and a process
| being controlled. When a connection is
| established, the process being controlled
| returns an interfaces::Init pointer to the
| controlling process, which the controlling
| process can use to get access to other
| interfaces and functionality.
|
| When spawning a new process, the steps are:
|
| 1. The controlling process calls
| interfaces::Ipc::spawnProcess(), which
| calls ipc::Process::spawn(), which spawns
| a new process and returns a socketpair file
| descriptor for communicating with it.
| interfaces::Ipc::spawnProcess() then calls
| ipc::Protocol::connect() passing the
| socketpair descriptor, which returns
| a local proxy interfaces::Init
| implementation calling remote
| interfaces::Init methods.
|
| 2. The spawned process calls
| interfaces::Ipc::startSpawnProcess(), which
| calls ipc::Process::checkSpawned() to read
| command line arguments and determine
| whether it is a spawned process and what
| socketpair file descriptor it should
| use. It then calls ipc::Protocol::serve()
| to handle incoming requests from the
| socketpair and invoke interfaces::Init
| interface methods, and exit when the socket
| is closed.
|
| 3. The controlling process calls local proxy
| interfaces::Init object methods to make
| other proxy objects calling other remote
| interfaces. It can also destroy the initial
| interfaces::Init object to close the
| connection and shut down the spawned
| process.
*/
///--------------------------
///--------------------------
///----------------------------------------