Expose ClientSession details to Host Extensions

remoting/host/security_key/gnubby_extension.cc

 // Copyright 2016 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.
 
 #include "remoting/host/security_key/gnubby_extension.h"
 
 #include "base/memory/ptr_util.h"
 #include "remoting/host/security_key/gnubby_extension_session.h"
 
 namespace {
 // TODO(joedow): Update this once clients support sending a gnubby capabililty.
 //               Tracked via: crbug.com/587485
 const char kCapability[] = "";
 }
 
 namespace remoting {
 
 GnubbyExtension::GnubbyExtension() {}
 
 GnubbyExtension::~GnubbyExtension() {}
 
 std::string GnubbyExtension::capability() const {
   return kCapability;
 }
 
 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));
 }
 
 }  // namespace remoting