Add the plumbing that will carry a clipboard item from a chromoting client to a host.

remoting/proto/event.proto

 // Copyright (c) 2012 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.
 
 // Protocol for event messages.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
@@ skipping 30 matching lines @@
   // These values encode the number of wheel 'ticks' (sometimes called
   // 'clicks' although 'ticks' is the most common cross-platform term).
   // Additional fields may be added later to support high-resolution devices.
   optional int32 wheel_offset_x = 3;
   optional int32 wheel_offset_y = 4;
 
   // Mouse button event.
   optional MouseButton button = 5;
   optional bool button_down = 6;
 }
+
+// Defines an event that sends clipboard data between peers.
+message ClipboardEvent {
+
+  // The type of the data being sent.
+  enum DataType {
+    DATA_TYPE_TEXT_UTF8 = 0;

[garykac, 2012/03/09 00:51:19]

Is the UTF8 suffix redundant or is the plan to support different text encodings
(SJIS, KOI8, Big5)?  Or is this just to allow alternate Unicode formats (like
UCS2)?

Supporting different text encodings doesn't seem worthwhile nor does supporting
UCS2 as an option (Japanese text requires 50% more storage with UTF8 vs UCS2,
but this isn't critical).

I would recommend using only UTF8 for text and naming this simply DATA_TYPE_TEXT
(with a comment noting that it's UTF8 encoded).

[simonmorris, 2012/03/09 00:53:24]

OK - I agree that we only want UTF-8.

+  }
+  required DataType dataType = 1;
+
+  // The data being sent.
+  required bytes data = 2;
+}