Video Capture Mojo (1.4a.a): Add service configurator interface

services/video_capture/public/interfaces/video_capture_device_access.mojom

Index: services/video_capture/public/interfaces/video_capture_device_access.mojom
diff --git a/services/video_capture/public/interfaces/video_capture_device.mojom b/services/video_capture/public/interfaces/video_capture_device_access.mojom
similarity index 96%
rename from services/video_capture/public/interfaces/video_capture_device.mojom
rename to services/video_capture/public/interfaces/video_capture_device_access.mojom
index ab6ff330c03891ad61f54aaf2c3b2f09045123b2..71e3cd106565826c45e278a75b2ae21531ab52cb 100644
--- a/services/video_capture/public/interfaces/video_capture_device.mojom
+++ b/services/video_capture/public/interfaces/video_capture_device_access.mojom
@@ -22,7 +22,7 @@ enum PowerLineFrequency {
 // Represents access to a video capture device available on the machine.
 // Note: Instead of offering an explicit Stop() method, the VideoCaptureDevice
 // is stopped automatically when the corresponding message pipe is closed.
-interface VideoCaptureDevice {
+interface VideoCaptureDeviceAccess {

[mcasas, 2016/08/12 23:38:37]

Why the name change? If the concern is that there is
already a media::VideoCaptureDevice that would make 
it confusing vis-a-vis the local
video_capture::VideoCaptureDevice, I'd propose
 VideoCaptureDeviceProxy and CreateDeviceProxy() ? 
(in this file and the other .mojom, resp).

[chfremer, 2016/08/15 20:10:34]

The concern is that instances of this interface represent access to a device and
not the device itself. The purpose of the rename was to reveal that more clearly
in the interface name. The name "VideoCaptureDeviceProxy" will work for that as
well, so let me follow your suggestion.

   Start(VideoCaptureFormat requested_format,
         ResolutionChangePolicy resolution_change_policy,
         PowerLineFrequency power_line_frequency,