Embed a mojo ApplicationManager in content/browser

content/public/browser/mojo_shell_context.h

+// Copyright 2015 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 CONTENT_PUBLIC_BROWSER_MOJO_SHELL_CONTEXT_H_
+#define CONTENT_PUBLIC_BROWSER_MOJO_SHELL_CONTEXT_H_
+
+#include "base/callback_forward.h"
+#include "base/macros.h"
+#include "content/common/content_export.h"
+
+namespace content {
+
+class ApplicationRegistry;
+
+// The global Mojo shell context for content embedders. By default this will
+// load new application instances in a utility process.
+class CONTENT_EXPORT MojoShellContext {

[jam, 2015/05/27 16:05:36]

why is this interface in public? i can't tell what will be used outside content
in the future.

(btw if you haven't seen it already,
https://www.chromium.org/developers/content-module/content-api is a good summary
of what goes in content/public)

[Ken Rockot(use gerrit already), 2015/05/27 19:36:16]

Doh. This is public because the first iteration of this patch had the embedder
providing an implementation. It is totally unnecessary now, so fixed.

+ public:
+  MojoShellContext() {}
+  virtual ~MojoShellContext() {}
+
+  static scoped_ptr<MojoShellContext> Create();
+
+  static void SetApplicationRegistryInitializerForTesting(
+      const base::Callback<void(ApplicationRegistry*)>& callback);
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(MojoShellContext);
+};
+
+}  // namespace content
+
+#endif  // CONTENT_PUBLIC_BROWSER_MOJO_SHELL_CONTEXT_H_