Embed a mojo ApplicationManager in content/browser

content/common/process_control.mojom

Index: content/common/process_control.mojom
diff --git a/content/common/process_control.mojom b/content/common/process_control.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..962a62508ed17b18bb3714be6aae31c880b80839
--- /dev/null
+++ b/content/common/process_control.mojom
@@ -0,0 +1,18 @@
+// 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.
+
+module content;
+
+import "mojo/application/public/interfaces/application.mojom";
+
+enum LoadApplicationResult {
+  OK,
+  NOT_FOUND,

[jam, 2015/05/29 01:48:54]

why is this an enum instead of a boolean?

[Ken Rockot(use gerrit already), 2015/05/29 03:20:40]

Done. It was an enum in anticipation of additional future failure modes (e.g.
when we support loading dynamic applications you might have an invalid binary), 
we can change it back to an enum when that happens.

+};
+
+interface ProcessControl {
+  LoadApplication(string url, mojo.Application& request)
+      => (LoadApplicationResult result);
+};
+