Move move classes to the remoting::protocol namespace. Minor cleanups.

remoting/protocol/host_message_dispatcher.cc

 // 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.
 
 #include "base/ref_counted.h"
 #include "net/base/io_buffer.h"
 #include "remoting/proto/control.pb.h"
 #include "remoting/proto/event.pb.h"
+#include "remoting/proto/internal.pb.h"

[Alpha Left Google, 2010/12/02 19:41:59]

also here, why is this needed? I thought we are going to depending less on
internal.pb.h, is this an intermediate step?

[Sergey Ulanov, 2010/12/02 20:06:40]

Because I moved ControlMessage to internal.proto. internal.proto is for the
container messages that are used by the protocol code, but should not be used by
anything outside of remoting/protocol.

 #include "remoting/protocol/host_message_dispatcher.h"
 #include "remoting/protocol/host_stub.h"
 #include "remoting/protocol/input_stub.h"
 #include "remoting/protocol/message_reader.h"
 #include "remoting/protocol/session.h"
 
 namespace {
 
 // A single protobuf can contain multiple messages that will be handled by
 // different message handlers.  We use this wrapper to ensure that the
@@ skipping 74 matching lines @@
     }
     if (message->event(i).has_mouse()) {
       input_stub_->InjectMouseEvent(
           &message->event(i).mouse(), NewDeleteTask(ref_msg));
     }
   }
 }
 
 }  // namespace protocol
 }  // namespace remoting