Implement ServiceManager

mojo/shell/shell.mojom

Index: mojo/shell/shell.mojom
diff --git a/mojo/shell/shell.mojom b/mojo/shell/shell.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..153baacfbe0b5b1cb3171db732dcb55321652ab1
--- /dev/null
+++ b/mojo/shell/shell.mojom
@@ -0,0 +1,18 @@
+// Copyright 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.
+
+module shell {
+
+[Peer=ShellClient]
+interface Shell {
+  // Loads lib|app_name|.so relative to the parent application.

[darin (slow to review), 2013/12/10 06:12:36]

nit: It might be nice to abstract this and just say that the string parameter is
a URL string. Then, the mapping mojo:// URLs to apps can be a detail of the
service manager.

If the URL is a http:// URL, then we would download the .so and load it :)

[DaveMoore, 2013/12/11 18:56:44]

Done.

+  void Connect(string app_name, handle<message_pipe> client_pipe);
+};
+
+[Peer=Shell]
+interface ShellClient {
+  void Connect(handle<message_pipe> client_pipe);

[darin (slow to review), 2013/12/10 06:12:36]

For apps that handle multiples URLs (or have multiple names), it might be nice
to see what URL / name they are being invoked as.

Also, I feel like "Connect" is not quite the right name for this method. This
method is an event to handle an incoming client connection. "AcceptConnection"
or "OnAcceptConnection"? I'm not sure if we want to standardize on using the
"On" prefix for events.

Perhaps there should also be a notification back to the guy who invoked
Shell::Connect() to tell them whether or not the connection was successful? Or,
should he just assume it was successful and then just monitor client_pipe to see
if it gets closed?

[DaveMoore, 2013/12/11 18:56:44]

Changed to AcceptConnection();
On 2013/12/10 06:12:36, darin wrote:

+};
+
+}