Lines Matching +full:client +full:- +full:id

2 ControlMaster connection-sharing.
14 Most messages from the client to the server contain a "request id"
15 field. This field is returned in replies as "client request id" to
18 Many multiplexing (mux) client requests yield immediate responses from
27 Unix domain control socket. The passenger client then waits until it is
29 the client waits around while the mux server does all the driving.
32 example of passenger mode; the client passes the stdio file descriptors
36 this mode, the mux client/server connection socket will stop speaking
38 messages between the client and server. The client therefore must
42 supporting a proxy client may itself be forwarded or relayed to another
48 ControlMaster from a client ssh(1), the first action of each is send
57 The current version of the mux protocol is 4. A client should refuse
65 To open a new multiplexed session in passenger mode, a client sends the
69 uint32 request id
85 The client then sends its standard input, output and error file
93 uint32 client request id
94 uint32 session id
100 indicating that the session is up. The client now waits for the
105 uint32 session id
108 The client should exit with this value to mimic the behaviour of a
109 non-multiplexed ssh(1) connection. Two additional cases that the
110 client must cope with are it receiving a signal itself and the
114 if remote TTY allocation was unsuccessful. The client may use this to
118 uint32 session id
120 3. Requesting passenger-mode stdio forwarding
122 A client may request the master to establish a stdio forwarding:
125 uint32 request id
130 The client then sends its standard input and output file descriptors
140 The client may request a health check/PID report from a server:
143 uint32 request id
148 uint32 client request id
153 A client may request that a master terminate immediately:
156 uint32 request id
162 A client may request the master to establish a port forward:
165 uint32 request id
174 If listen port is (unsigned int) -2, then the listen host is treated as
177 If connect port is (unsigned int) -2, then the connect host is treated
186 uint32 client request id
191 A client may request the master to close a port forward:
194 uint32 request id
206 A client may request the master to stop accepting new multiplexing requests
210 uint32 request id
217 A client may request that the control connection be placed in proxy
221 uint32 request id
227 uint32 request id
235 byte[packet length - 2] ...
238 and will translate channel identifiers to ensure that the proxy client has
239 globally unique channel numbers (i.e. a proxy client need not worry about
247 uint32 client request id
252 uint32 client request id
256 uint32 client request id
287 XXX server->client error/warning notifications
290 XXX extensions for multi-agent
291 XXX extensions for multi-X11