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

remoting/protocol/client_control_sender.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.
 
 // This stub is thread safe because of the use of BufferedSocketWriter.
 // BufferedSocketWriter buffers messages and send them on them right thread.
 
 #include "remoting/protocol/client_control_sender.h"
 
 #include "base/task.h"
 #include "remoting/protocol/buffered_socket_writer.h"
 #include "remoting/proto/control.pb.h"
+#include "remoting/proto/internal.pb.h"

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

why is this needed?

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

Because I moved ControlMessage to internal.proto.

 #include "remoting/protocol/util.h"
 
 namespace remoting {
 namespace protocol {
 
 ClientControlSender::ClientControlSender(net::Socket* socket)
     : buffered_writer_(new BufferedSocketWriter()) {
   buffered_writer_->Init(socket, NULL);
 }
 
 ClientControlSender::~ClientControlSender() {
 }
 
 void ClientControlSender::NotifyResolution(
     const NotifyResolutionRequest* msg, Task* done) {
-  ControlMessage message;
+  protocol::ControlMessage message;
   message.mutable_notify_resolution()->CopyFrom(*msg);
   buffered_writer_->Write(SerializeAndFrameMessage(message));
   done->Run();
   delete done;
 }
 
 }  // namespace protocol
 }  // namespace remoting