Changed MessageReader so that it doesn't read from the socket if there are

remoting/proto/event.proto

 // Copyright (c) 2010 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 24 matching lines @@
   // Mouse wheel information.
   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 message on the event channel.
-message Event {
+message EventMessage {

[awong, 2011/01/20 20:06:38]

Nit, I would just called his "event" or better "InputEvent"

[Sergey Ulanov, 2011/01/20 21:55:57]

I think it is better to call it EventMessage for consistency with
ControlMessage. Moved this to internal.proto.

   required int32 timestamp = 1;  // Client timestamp for event
   optional bool dummy = 2;       // Is this a dummy event?
 
   optional KeyEvent key = 3;
   optional MouseEvent mouse = 4;
 }
-
-// Message sent in the event channel.
-message EventMessage {
-  repeated Event event = 1;
-}