Download the host components when user tries to enable Me2Me host.

remoting/webapp/host_controller.js

Index: remoting/webapp/host_controller.js
diff --git a/remoting/webapp/host_controller.js b/remoting/webapp/host_controller.js
index 21485b12554416ca61e847505cb4114697aa27f6..628b82398c1b79e6c9f07c5152356a4de33800ba 100644
--- a/remoting/webapp/host_controller.js
+++ b/remoting/webapp/host_controller.js
@@ -15,6 +15,10 @@ remoting.HostController = function() {
     /** @type {HTMLElement} @private */
     var container = document.getElementById('daemon-plugin-container');
     container.appendChild(plugin);
+    if (plugin.getDaemonState === undefined) {

[weitao, 2014/01/31 18:37:11]

Remoting.js uses a different way of detecting the plugin:

plugin.hasOwnProperty('REQUESTED_ACCESS_CODE');

Which is the preferred way?

I recommend having an isNpapiPluginSupported() function in remoting.js that
unifies all these checks.

[Sergey Ulanov, 2014/01/31 23:34:17]

It's essentially the same, except we are using different properties.
hasOwnProperty() is slightly better because it doesn't look at the object's
prototype.
I don't think it's worth worrying about it much. Hopefully we can remove all
NPAPI-related code soon. I'm working another CL to integrate download in It2Me
flow - I'll need to refactor plugin loading for It2Me, so I'll make sure the
plugin loading code is shared..

+      container.removeChild(plugin);
+      return null;
+    }
     return plugin;
   };