Touch Events capability negotiation

remoting/host/remoting_me2me_host.cc

Index: remoting/host/remoting_me2me_host.cc
diff --git a/remoting/host/remoting_me2me_host.cc b/remoting/host/remoting_me2me_host.cc
index 96fe46e40165ff34fb2a592013ed555494c8eaff..af08d636ea0ea4ef138d81a8f73b326e34516d76 100644
--- a/remoting/host/remoting_me2me_host.cc
+++ b/remoting/host/remoting_me2me_host.cc
@@ -58,6 +58,7 @@
 #include "remoting/host/ipc_host_event_logger.h"
 #include "remoting/host/logging.h"
 #include "remoting/host/me2me_desktop_environment.h"
+#include "remoting/host/multi_touch_capability.h"
 #include "remoting/host/pairing_registry_delegate.h"
 #include "remoting/host/policy_watcher.h"
 #include "remoting/host/session_manager_factory.h"
@@ -818,6 +819,7 @@ void HostProcess::StartOnUiThread() {
 
   desktop_environment_factory_.reset(desktop_environment_factory);
   desktop_environment_factory_->SetEnableGnubbyAuth(enable_gnubby_auth_);
+  desktop_environment_factory_->SetEnableMultiTouch(MultiTouchCapable());

[Wez, 2015/03/30 17:10:07]

Do you need to have the Me2Me host do this? You're just enabling/disabling based
on whether the implementation supports touch - you can do that my exposing that
information on the InputStub or InputInjector interfaces, and letting the
DesktopEnvironment or ClientSession then use that to construct the capabilities
it reports.

[Rintaro Kuroiwa, 2015/04/08 03:27:43]

All I really wanted to do is unit test that "multiTouch" is added to the host
capabilities. Adding a (non-static) CanInjectTouch() method to InputInjector, I
should be able to do this in client_session_unittest.cc :)

 
   context_->network_task_runner()->PostTask(
       FROM_HERE,