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

remoting/host/event_executor_linux.cc

Index: remoting/host/event_executor_linux.cc
diff --git a/remoting/host/event_executor_linux.cc b/remoting/host/event_executor_linux.cc
index b1829ec987a93091471ee9ddd379b8bed185001f..bde0ec43eb11836a380819bc0c297ebe99894033 100644
--- a/remoting/host/event_executor_linux.cc
+++ b/remoting/host/event_executor_linux.cc
@@ -20,8 +20,8 @@
 
 namespace remoting {
 
-using protocol::MouseEvent;
 using protocol::KeyEvent;
+using protocol::MouseEvent;
 
 namespace {
 
@@ -37,6 +37,11 @@ class EventExecutorLinux : public EventExecutor {
 
   bool Init();
 
+  // Clipboard stub interface.
+  virtual void InjectClipboardEvent(const protocol::ClipboardEvent& event)

[Wez, 2012/03/15 01:14:44]

nit: Be consist about protocol::ClipboardEvent vs KeyEvent / MouseEvent?  Have
you avoided using for ClipboardEvent because it's only used in two places?

[simonmorris, 2012/03/15 16:53:19]

I was consistent originally, but another reviewer asked for the change. Now it's
2-1, so I've gone back to the consistent approach.

+      OVERRIDE;
+
+  // InputStub interface.
   virtual void InjectKeyEvent(const KeyEvent& event) OVERRIDE;
   virtual void InjectMouseEvent(const MouseEvent& event) OVERRIDE;
 
@@ -314,6 +319,11 @@ bool EventExecutorLinux::Init() {
   return true;
 }
 
+void EventExecutorLinux::InjectClipboardEvent(
+    const protocol::ClipboardEvent& event) {
+  // TODO(simonmorris): Implement clipboard injection.
+}
+
 void EventExecutorLinux::InjectKeyEvent(const KeyEvent& event) {
   if (MessageLoop::current() != message_loop_) {
     message_loop_->PostTask(