Chromium Code Reviews| Index: remoting/protocol/client_control_sender.cc |
| diff --git a/remoting/protocol/client_control_sender.cc b/remoting/protocol/client_control_sender.cc |
| index 8fff96762065c9ab229791cc78b3f4e536e9e6f4..d1fd2f5fd5ad3ca84181f2cd3edc89b8b8b1475d 100644 |
| --- a/remoting/protocol/client_control_sender.cc |
| +++ b/remoting/protocol/client_control_sender.cc |
| @@ -10,6 +10,7 @@ |
| #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 { |
| @@ -25,7 +26,7 @@ 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(); |