Use VP8 over PseudoTCP by default.

remoting/host/event_executor.h

Index: remoting/host/event_executor.h
diff --git a/remoting/host/event_executor.h b/remoting/host/event_executor.h
new file mode 100644
index 0000000000000000000000000000000000000000..2bfd67d51f5388ec8f758bc98d4f7d46f298d766
--- /dev/null
+++ b/remoting/host/event_executor.h
@@ -0,0 +1,24 @@
+// 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.
+
+#ifndef REMOTING_HOST_EVENT_EXECUTOR_H_
+#define REMOTING_HOST_EVENT_EXECUTOR_H_
+
+#include "remoting/protocol/input_stub.h"
+
+class MessageLoop;
+
+namespace remoting {
+
+class Capturer;
+
+// Base class for event executors.
+class EventExecutor : public protocol::InputStub {

[Alpha Left Google, 2010/11/23 00:38:25]

We'll make EventExecutor go away so create a static factory method defined in
event_executor.h but no need define a new class.

[Sergey Ulanov, 2010/11/23 01:59:18]

I think it is still better to have EventExecutor class:
 1. It shows that EventExecutorWin, EventExecutorLinux and EventExecutorMac are
related to each other.
 2. We may need to add some other methods in here that are not part of
InputStub.
 3. It might be necessary to share some implementation details between different
event executors (e.g. event queuing).
 4. EventExecutor::Create() looks better than CreateEventExecutor().

[Alpha Left Google, 2010/11/23 05:15:24]

I suggest we add such class when we need it. Right now I still don't see what is
needed more than this just the InputStub interface. And it is supposed to just
implement the InputStub interface..

+ public:
+  static EventExecutor* Create(MessageLoop* message_loop, Capturer* capturer);
+};
+
+}  // namespace remoting
+
+#endif  // REMOTING_HOST_EVENT_EXECUTOR_H_