Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(693)

Side by Side Diff: remoting/host/chromoting_messages.h

Issue 2478443002: Use ChannelMojo for remote security key channels. (Closed)
Patch Set: Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright (c) 2012 The Chromium Authors. All rights reserved. 1 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 #ifndef REMOTING_HOST_CHROMOTING_MESSAGES_H_ 5 #ifndef REMOTING_HOST_CHROMOTING_MESSAGES_H_
6 #define REMOTING_HOST_CHROMOTING_MESSAGES_H_ 6 #define REMOTING_HOST_CHROMOTING_MESSAGES_H_
7 7
8 #include <stdint.h> 8 #include <stdint.h>
9 9
10 #include "base/memory/shared_memory_handle.h" 10 #include "base/memory/shared_memory_handle.h"
(...skipping 231 matching lines...) Expand 10 before | Expand all | Expand 10 after
242 // Chromoting messages sent from the remote_security_key process to the 242 // Chromoting messages sent from the remote_security_key process to the
243 // network process. 243 // network process.
244 244
245 // The array of bytes representing a security key request to be sent to the 245 // The array of bytes representing a security key request to be sent to the
246 // remote client. 246 // remote client.
247 IPC_MESSAGE_CONTROL1(ChromotingRemoteSecurityKeyToNetworkMsg_Request, 247 IPC_MESSAGE_CONTROL1(ChromotingRemoteSecurityKeyToNetworkMsg_Request,
248 std::string /* request bytes */) 248 std::string /* request bytes */)
249 249
250 //--------------------------------------------------------- 250 //---------------------------------------------------------
251 // Chromoting messages sent from the network process to the remote_security_key 251 // Chromoting messages sent from the network process to the remote_security_key
252 // process. The network process uses two types of IPC channels to communicate 252 // process.
253 // with the remote_security_key process. The first is the 'service' channel.
254 // It uses a hard-coded path known by the client and server classes and its job
255 // is to create a new, private IPC channel for the client and provide the path
256 // to that channel over the original IPC channel. This purpose for this
257 // mechanism is to allow the network process to service multiple concurrent
258 // security key requests. Once a client receives the connection details for
259 // its private IPC channel, the server channel is reset and can be called by
260 // another client.
261 // The second type of IPC channel is strictly used for passing security key
262 // request and response messages. It is destroyed once the client disconnects.
263
264 // The IPC channel path for this remote_security_key connection. This message
265 // is sent from the well-known IPC server channel.
266 IPC_MESSAGE_CONTROL1(ChromotingNetworkToRemoteSecurityKeyMsg_ConnectionDetails,
267 std::string /* IPC Server path */)
268 253
269 // The array of bytes representing a security key response from the remote 254 // The array of bytes representing a security key response from the remote
270 // client. This message is sent over the per-client IPC channel. 255 // client. This message is sent over the per-client IPC channel.
271 IPC_MESSAGE_CONTROL1(ChromotingNetworkToRemoteSecurityKeyMsg_Response, 256 IPC_MESSAGE_CONTROL1(ChromotingNetworkToRemoteSecurityKeyMsg_Response,
272 std::string /* response bytes */) 257 std::string /* response bytes */)
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698