Integrating Online Wallet into Chrome.

chrome/common/chrome_switches.cc

Index: chrome/common/chrome_switches.cc
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 67931de9f86804ff66fbe8584ba5e83d632eeea7..97e938b8baac3bf5994a01e6ce6f1295876dbb40 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -1360,6 +1360,12 @@ const char kViewerConnection[]              = "viewer-connection";
 // Cycle through a series of URLs listed in the specified file.
 const char kVisitURLs[]                     = "visit-urls";
 
+// Secure service URL for Online Wallet service.
+const char kWalletSecureServiceUrl[]        = "wallet-secure-service-url";
+
+// Service URL for Online Wallet service.
+const char kWalletServiceUrl[]              = "wallet-service-url";

[Ilya Sherman, 2012/12/15 01:40:12]

Why do we have a non-secure URL (that we're willing to use) for the service? 
These flags should probably be documented better to explain what they mean.

[ahutter, 2012/12/15 02:22:22]

Done.

[benquan, 2012/12/15 02:48:59]

I would suggest to use a different word other than "secure", as people leaning
to think about "https:" when they saw "secure" and "url" in the constant name.

On 2012/12/15 02:22:22, ahutter wrote:

[ahutter, 2012/12/17 17:23:02]

Added some comments.

+
 // Enable the "native services" feature of web-intents.
 const char kWebIntentsNativeServicesEnabled[] =
     "web-intents-native-services-enabled";