Rename (Host|Client)Message to Chromoting(Host|Client)Message.

Rename HostMessage and ClientMessage to Chromoting{Host|Client}Message to
avoid conflicts with messages in X11.

Actually, only ClientMessage needs to be changed due to conflict, but HostMessage is changed to keep the names consistent.

BUG=none
TEST=remoting unittests

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=57112

Review URL: http://codereview.chromium.org/3161034

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57255 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 2 insertions, 2 deletions

diff --git a/remoting/base/protocol/chromotocol.proto b/remoting/base/protocol/chromotocol.proto
index df510d9..f2752d9 100644
--- a/remoting/base/protocol/chromotocol.proto
+++ b/remoting/base/protocol/chromotocol.proto
@@ -99,7 +99,7 @@ message UpdateStreamPacketMessage {
 // Defines the message that is sent from the host to the client.
 // Only one of these messages should be present.
 // NEXT ID: 5
-message HostMessage {
+message ChromotingHostMessage {
   optional InitClientMessage init_client= 1;
   optional BeginUpdateStreamMessage begin_update_stream = 2;
   optional EndUpdateStreamMessage end_update_stream = 3;
@@ -162,7 +162,7 @@ message MouseUpEvent {
 // Defines the message that is sent from the client to the host.
 // Only one of the optional messages should be present.
 // NEXT ID: 7
-message ClientMessage {
+message ChromotingClientMessage {
   optional KeyEvent key_event = 1;
   optional MouseSetPositionEvent mouse_set_position_event = 2;
   optional MouseMoveEvent mouse_move_event = 3;