Package video capture skeleton as Mojo Shell Service

services/video_capture/service_manifest.json

Index: services/video_capture/service_manifest.json
diff --git a/services/video_capture/service_manifest.json b/services/video_capture/service_manifest.json
new file mode 100644
index 0000000000000000000000000000000000000000..1f8aaf92ea2fe7ac98cc9d9c1730c558a893c111
--- /dev/null
+++ b/services/video_capture/service_manifest.json
@@ -0,0 +1,13 @@
+{
+  "manifest_version":  1,
+  "name": "mojo:video_capture",
+  "display_name": "Video Capture",
+  "capabilities": {
+    "provided": {
+      "all": ["*"]

[Ben Goodger (Google), 2016/08/15 22:56:48]

Help me understand the interfaces you expect to bind from tests.

Are some unsafe to be seen by renderers? By other specific process types?

[chfremer, 2016/08/15 23:19:47]

The service is supposed to have two types of clients. The first client is a
component called VideoCaptureManager, which lives in the Browser process and
whose responsibility it is to distribute access to (and video frames from) the
video capture devices to potentially multiple clients. These clients typically
live in the renderers. 

The second type of client is a component test for the service.

There may or may not be some interfaces that are exclusive to the testing client
in the end. At this stage, we only have the testing client, so I am not (yet)
distinguishing different classes of provided-interfaces.

Is there anything I need to do to hide this service from renderers?

+    },
+    "required": {
+      "mojo:shell": { "classes": [ "shell:all_users" ] }
+    }
+  }
+}