[Chromoting] Request the daemon to open a terminal once a connection has been accepted.

remoting/host/desktop_environment_factory.h

Index: remoting/host/desktop_environment_factory.h
diff --git a/remoting/host/desktop_environment_factory.h b/remoting/host/desktop_environment_factory.h
index 9bbd71c165699b77b0a5dea19463ea700a3eba4e..1f89967f9bad1259cb0fd5dd873ff27306f938df 100644
--- a/remoting/host/desktop_environment_factory.h
+++ b/remoting/host/desktop_environment_factory.h
@@ -15,6 +15,7 @@ class SingleThreadTaskRunner;
 
 namespace remoting {
 
+class ChromotingHost;
 class DesktopEnvironment;
 
 class DesktopEnvironmentFactory {
@@ -24,7 +25,9 @@ class DesktopEnvironmentFactory {
       scoped_refptr<base::SingleThreadTaskRunner> ui_task_runner);
   virtual ~DesktopEnvironmentFactory();
 
-  virtual scoped_ptr<DesktopEnvironment> Create();
+  // Creates an instance of |DesktopEnvironment| to be used by |host|.
+  virtual scoped_ptr<DesktopEnvironment> Create(
+      scoped_refptr<ChromotingHost> host);

[Wez, 2012/10/17 17:51:57]

Since DesktopEnvironments are created per-client, why not pass the client here?
:)

[Wez, 2012/10/17 17:51:57]

If you really need to pass the |host| here then pass it to the factory-specific
ctor, rather than to the Create() method.

[alexeypa (please no reviews), 2012/10/17 21:35:53]

Done.

[alexeypa (please no reviews), 2012/10/17 21:35:53]

Ack.

[Wez, 2012/10/17 22:04:24]

The more I think about it, the more I think I'd prefer that you pass the
ChromotingHost to the factory-specific ctor, but arguably this approach is more
future-proof.

 
   // Returns |true| if created |DesktopEnvironment| instances support audio
   // capture.