Create services/gcm directory and add some initial files

chrome/browser/services/gcm/gcm_profile_service.h

Index: chrome/browser/services/gcm/gcm_profile_service.h
diff --git a/chrome/browser/services/gcm/gcm_profile_service.h b/chrome/browser/services/gcm/gcm_profile_service.h
new file mode 100644
index 0000000000000000000000000000000000000000..3650deb78444f77eeb6a066c75e7c04a660018da
--- /dev/null
+++ b/chrome/browser/services/gcm/gcm_profile_service.h
@@ -0,0 +1,33 @@
+// Copyright (c) 2013 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.
+
+#ifndef CHROME_BROWSER_SERVICES_GCM_GCM_PROFILE_SERVICE_H_
+#define CHROME_BROWSER_SERVICES_GCM_GCM_PROFILE_SERVICE_H_
+
+#include "base/basictypes.h"
+#include "components/browser_context_keyed_service/browser_context_keyed_service.h"
+
+class Profile;
+
+namespace gcm {
+
+// Acts as a bridge between GCM API and GCMClient layer. It is profile based.
+class GCMProfileService : public BrowserContextKeyedService {
+ public:
+  explicit GCMProfileService(Profile* profile);
+  virtual ~GCMProfileService();
+
+  // Returns true if the GCM support is enabled.
+  static bool IsGCMEnabled();

[fgorski, 2013/11/05 19:40:18]

What are the advantages/disadvantages of having that as a static on the service
class as opposed to having it on the service factory (perhaps as a static)?

+
+ private:
+  // The profile which owns this object.
+  Profile* profile_;
+
+  DISALLOW_COPY_AND_ASSIGN(GCMProfileService);
+};
+
+}  // namespace gcm
+
+#endif  // CHROME_BROWSER_SERVICES_GCM_GCM_PROFILE_SERVICE_H_