Add service registration for apps APIs implemented as mojo services.

extensions/browser/mojo/service_registration_manager.h

Index: extensions/browser/mojo/service_registration_manager.h
diff --git a/extensions/browser/mojo/service_registration_manager.h b/extensions/browser/mojo/service_registration_manager.h
new file mode 100644
index 0000000000000000000000000000000000000000..eb123f4cd33434fa7ac930f74da47d2145305fb7
--- /dev/null
+++ b/extensions/browser/mojo/service_registration_manager.h
@@ -0,0 +1,94 @@
+// Copyright 2014 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 EXTENSIONS_BROWSER_MOJO_SERVICE_REGISTRATION_MANAGER_H_
+#define EXTENSIONS_BROWSER_MOJO_SERVICE_REGISTRATION_MANAGER_H_
+
+#include <string>
+#include <utility>
+#include <vector>
+
+#include "base/callback.h"
+#include "base/memory/linked_ptr.h"
+#include "content/public/common/service_registry.h"
+#include "mojo/public/cpp/bindings/interface_request.h"
+
+namespace content {
+class RenderFrameHost;
+}
+
+namespace extensions {
+namespace internal {
+
+// A base class for forwarding calls to ServiceRegistry::AddService().
+class ServiceFactoryBase {
+ public:
+  virtual ~ServiceFactoryBase() {}
+
+  // Add this service factory to |service_registry|.
+  virtual void Register(content::ServiceRegistry* service_registry) const = 0;
+};
+
+template <typename Interface>
+class ServiceFactory : public ServiceFactoryBase {
+ public:
+  explicit ServiceFactory(
+      const base::Callback<void(mojo::InterfaceRequest<Interface>)>& factory)

[Ken Rockot(use gerrit already), 2014/10/24 16:36:14]

I agree with Raymes on the confusing nature of this type, but I'm not convinced
it can be made less confusing with any sort of type alias. Any alternative I can
think of will still be a relatively complex type expression
(FooSomething<Interface>::SomeCallbackType) and will only serve to mask the
underlying equally-complex type expression.

Fortunately I think the example of actually registering the serial service
clarifies the usage for anyone trying to understand this code, so I'm not sure
anything needs to change here.

+      : factory_(factory) {}
+  ~ServiceFactory() override {}
+
+  void Register(content::ServiceRegistry* service_registry) const override {
+    service_registry->AddService(factory_);
+  }
+
+ private:
+  const base::Callback<void(mojo::InterfaceRequest<Interface>)> factory_;
+  DISALLOW_COPY_AND_ASSIGN(ServiceFactory);
+};
+
+}  // namespace internal
+
+// A meta service registry. This allows registration of service factories and
+// their associated extensions API permission name. Whenever a RenderFrameHost
+// is created, each service that the render frame should have access to (based
+// on its SiteInstance), is added to the ServiceRegistry for that
+// RenderFrameHost.
+class ServiceRegistrationManager {
+ public:
+  ServiceRegistrationManager();
+  ~ServiceRegistrationManager();
+
+  static ServiceRegistrationManager* GetSharedInstance();
+
+  // Registers a ServiceFactory to be provided to extensions with the
+  // |permission_name| API permission.
+  //
+  // TODO(sammc): Add support for service factories that take the Extension*
+  // (or extension ID) and BrowserContext to allow fine-grained service and
+  // permission customization.
+  template <typename Interface>
+  void AddServiceFactory(
+      const std::string& permission_name,

[Ken Rockot(use gerrit already), 2014/10/24 16:36:14]

nit: Maybe we could have a ServiceFilter type (which for now only supports
API-permission-name-based filtering) instead of just a string? Optional, not
sure it's worth doing right now, but maybe an alternative to taking extension
ID, BrowserContext, etc, directly.

[Sam McNally, 2014/10/26 23:17:31]

The TODO is about currying the Extension and/or BrowserContext into the service
factory so the service can do its own permission management.

That said, I think we will want to support more flexible coarse-grained
"permissions". Added a TODO for that too.

+      const base::Callback<void(mojo::InterfaceRequest<Interface>)>& factory) {
+    factories_.push_back(
+        std::make_pair(permission_name,
+                       linked_ptr<internal::ServiceFactoryBase>(
+                           new internal::ServiceFactory<Interface>(factory))));
+  }
+
+  // Adds the service factories appropriate for |render_frame_host| to its
+  // ServiceRegistry.
+  void AddServicesToRenderFrame(content::RenderFrameHost* render_frame_host);
+
+ private:
+  // All factories and their corresponding API permissions.
+  std::vector<std::pair<std::string, linked_ptr<internal::ServiceFactoryBase>>>
+      factories_;
+
+  DISALLOW_COPY_AND_ASSIGN(ServiceRegistrationManager);
+};
+
+}  // namespace extensions
+
+#endif  // EXTENSIONS_BROWSER_MOJO_SERVICE_REGISTRATION_MANAGER_H_