Expose ClientSession details to Host Extensions

remoting/host/security_key/gnubby_extension.cc

Index: remoting/host/security_key/gnubby_extension.cc
diff --git a/remoting/host/security_key/gnubby_extension.cc b/remoting/host/security_key/gnubby_extension.cc
index 3177766998bbd521328e2a1e8c6c7838b45fec9a..469baa1c60239e83334fa6195a209c40f8dddd9f 100644
--- a/remoting/host/security_key/gnubby_extension.cc
+++ b/remoting/host/security_key/gnubby_extension.cc
@@ -24,11 +24,12 @@ std::string GnubbyExtension::capability() const {
 }
 
 std::unique_ptr<HostExtensionSession> GnubbyExtension::CreateExtensionSession(
-    ClientSessionControl* client_session_control,
+    ClientSessionDetails* client_session_details,
     protocol::ClientStub* client_stub) {
   // TODO(joedow): Update this mechanism to allow for multiple sessions.  The
   //               extension will only send messages through the initial
   //               |client_stub| with the current design.
+  // TODO(joedow): Update GnubbyExtensionSession for |client_session_details|.

[Sergey Ulanov, 2016/06/27 19:51:30]

Not sure what this TODO is about. You did update GnubbyExtensionSession  in this
CL.

[joedow, 2016/06/27 21:07:28]

Ah, this CL updated GnubbyExtension, the next CL (mentioned in the TODO) updates
GnubbySessionExtension.  It is kind of confusing as the names are really similar
(like many of the Host classes).

   return base::WrapUnique(new GnubbyExtensionSession(client_stub));
 }