Use a distinct source parameter on gaia endpoints for the reconcilor.

google_apis/gaia/gaia_constants.cc

 // 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.
 //
 // Constants definitions
 
 #include "google_apis/gaia/gaia_constants.h"
 
 namespace GaiaConstants {
 
 // Gaia uses this for accounting where login is coming from.
 const char kChromeOSSource[] = "chromeos";
 const char kChromeSource[] = "ChromiumBrowser";
+const char kReconcilorSource[] = "ChromiumReconcilor";

[Mike Lerman, 2014/09/26 16:57:08]

Should the string be perhaps ChromiumBrowserReconcilor, so that GAIA-side
queries can easily group together all things Chromium with a prefix? Or will the
existing ^Chromium.* be sufficient, e.g. we're confident nothing else has that
same prefix?

[Roger Tawa OOO till Jul 10th, 2014/09/26 19:42:39]

Yup, already checked with them and this is string we settled on.

 
 // Service name for Gaia.  Used to convert to cookie auth.
 const char kGaiaService[] = "gaia";
 // Service name for Picasa API. API is used to get user's image.
 const char kPicasaService[] = "lh2";
 
 // Service/scope names for sync.
 const char kSyncService[] = "chromiumsync";
 
 // Service name for remoting.
@@ skipping 39 matching lines @@
 
 // Used to build ClientOAuth requests.  These are the names of keys used when
 // building base::DictionaryValue that represent the json data that makes up
 // the ClientOAuth endpoint protocol.  The comment above each constant explains
 // what value is associated with that key.
 
 // Canonical email of the account to sign in.
 const char kClientOAuthEmailKey[] = "email";
 
 }  // namespace GaiaConstants