Expose ClientSession details to Host Extensions

remoting/host/host_extension.h

Index: remoting/host/host_extension.h
diff --git a/remoting/host/host_extension.h b/remoting/host/host_extension.h
index 07c5b775a217b9aec1af5aed88bd933a47ccbf1a..eb4cb971eb3ac3b4b1285077e09d609c2a4315e5 100644
--- a/remoting/host/host_extension.h
+++ b/remoting/host/host_extension.h
@@ -8,10 +8,10 @@
 #include <memory>
 #include <string>
 
-
 namespace remoting {
 
 class ClientSessionControl;
+class ClientSessionDetails;
 class HostExtensionSession;
 
 namespace protocol {
@@ -34,10 +34,12 @@ class HostExtension {
   // Creates an extension session, which can handle extension messages for a
   // client session.
   // |client_session_control| may be used to e.g. disconnect the session.
+  // |client_session_details| provides details about the current client session.
   // |client_stub| may be used to send messages to the session.
   // Both interfaces are valid for the lifetime of the |HostExtensionSession|.
   virtual std::unique_ptr<HostExtensionSession> CreateExtensionSession(
       ClientSessionControl* client_session_control,
+      ClientSessionDetails* client_session_details,

[Sergey Ulanov, 2016/06/23 22:41:28]

Do we really need to have ClientSessionDetails separate from
ClientSessionControl? They are going to point to the same ClientSession object
and I don't see any good reason to separate them.

       protocol::ClientStub* client_stub) = 0;
 };