Touch Events capability negotiation

remoting/host/win/session_input_injector.cc

Index: remoting/host/win/session_input_injector.cc
diff --git a/remoting/host/win/session_input_injector.cc b/remoting/host/win/session_input_injector.cc
index bf8158ee1b7580f973efca7f46efc80971ce1135..333741311fb46679a4d7682acc13f4d5f82bd9c8 100644
--- a/remoting/host/win/session_input_injector.cc
+++ b/remoting/host/win/session_input_injector.cc
@@ -66,6 +66,7 @@ class SessionInputInjectorWin::Core
   virtual void InjectTextEvent(const TextEvent& event) override;
   virtual void InjectMouseEvent(const MouseEvent& event) override;
   virtual void InjectTouchEvent(const TouchEvent& event) override;
+  virtual bool CanInjectTouch() override;
 
  private:
   friend class base::RefCountedThreadSafe<Core>;
@@ -200,6 +201,10 @@ void SessionInputInjectorWin::Core::InjectTouchEvent(const TouchEvent& event) {
   nested_executor_->InjectTouchEvent(event);
 }
 
+bool SessionInputInjectorWin::Core::CanInjectTouch() {
+  return nested_executor_->CanInjectTouch();

[Wez, 2015/04/09 22:58:59]

You're accessing the |nested_executor_| from the caller thread, rather than from
the |input_task_runner_| thread.

Since we never expect the result to change at run-time, I'd suggest instead
calling CanInjectTouch() on the |input_task_runner_| and posting the result back
to the SessionInputInjectorWin (NOT the core) on the caller thread, to cache to
return from its own CanInjectTouch().

[Rintaro Kuroiwa, 2015/04/20 18:20:03]

N/A for latest patch.

+}
+
 SessionInputInjectorWin::Core::~Core() {
 }
 
@@ -256,4 +261,8 @@ void SessionInputInjectorWin::InjectTouchEvent(
   core_->InjectTouchEvent(event);
 }
 
+bool SessionInputInjectorWin::CanInjectTouch() {
+  return core_->CanInjectTouch();
+}
+
 }  // namespace remoting