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 {

[Wez, 2012/03/14 20:40:56]

I thought that we had agreed on TextClipboardEvent containing just a UTF-8
encoded string for now, with the intent being to move to a
multi-MIME-type-capable multi-channel protocol in future?

[simonmorris, 2012/03/14 21:20:21]

We may be able to use this message as it stands in such a protocol. Keeping the
MIME type in the message costs very little, and keeps that option open.

+
+  // The MIME type of the data being sent.
+  required string mime_type = 1;

[Sergey Ulanov, 2012/03/14 20:27:07]

It's usually better to mark all fields in protobuf messages as optional.
Otherwise it would be more difficult to make them optional in the future if we
need to.

[simonmorris, 2012/03/14 21:20:21]

Done.

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