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

remoting/proto/event.proto

Index: remoting/proto/event.proto
diff --git a/remoting/proto/event.proto b/remoting/proto/event.proto
index 19c734da97184e59818e2181faca4099d4296de2..10a6b8291606133b4cb324adef0bd530d9ea8cfe 100644
--- a/remoting/proto/event.proto
+++ b/remoting/proto/event.proto
@@ -42,15 +42,10 @@ message MouseEvent {
 }
 
 // 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;
-}