Added HostListApl implementation to connect to legacy directory and GCD.

remoting/webapp/base/js/plugin_settings.js

 // Copyright (c) 2012 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.
 
 // Contains all the settings that may need massaging by the build script.
 // Keeping all that centralized here allows us to use symlinks for the other
 // files making for a faster compile/run cycle when only modifying HTML/JS.
 
 'use strict';
 
@@ skipping 49 matching lines @@
     !!'XMPP_SERVER_USE_TLS';
 
 // Third party authentication settings.
 /** @type {string} The third party auth redirect URI. */
 remoting.Settings.prototype.THIRD_PARTY_AUTH_REDIRECT_URI =
     'THIRD_PARTY_AUTH_REDIRECT_URL';
 
 // 'native', 'nacl' or 'pnacl'.
 remoting.Settings.prototype.CLIENT_PLUGIN_TYPE = 'CLIENT_PLUGIN_TYPE';
 
 /** @const {boolean} If true, use GCD instead of Chromoting registry. */

[kelvinp, 2015/06/29 23:53:45]

It seems like after your change, we would always be running using the the
combined host list, can we remove USE_CCD?

[John Williams, 2015/07/17 23:29:33]

I removed PREFER_GCD and kept USE_GCD as the only way to quickly roll back
GCD-related functionality.

 remoting.Settings.prototype.USE_GCD = !!'USE_GCD';
+
+/**
+ * If true, data in GCD takes priority over conflicting data in the
+ * legacy registery.
+ * @const {boolean}
+ */
+remoting.Settings.prototype.PREFER_GCD = remoting.Settings.prototype.USE_GCD;