Implement Connector::ApplySpec() & use to enforce navigation:frame

services/service_manager/public/interfaces/connector.mojom

 // Copyright 2014 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 service_manager.mojom;
 
 import "services/service_manager/public/interfaces/interface_provider.mojom";
 
 // TODO(beng): Determine who (if anyone) uses kRootUserID.
 const string kRootUserID = "505C0EE9-3013-43C0-82B0-A84F50CF8D84";
@@ skipping 146 matching lines @@
   //   process may not have been launched by the time BindInterface() is
   //   called.)
   //
   StartServiceWithProcess(Identity target,
                           handle<message_pipe> service,
                           PIDReceiver& pid_receiver_request) =>
       (ConnectResult result, Identity identity);
 
   // Clones this Connector so it can be passed to another thread.
   Clone(Connector& request);
+
+  // Asks the Service Manager to enforce the rules contained in the
+  // InterfaceProviderSpec named |spec| in the calling service's service
+  // manifest on incoming interface requests from |source|.
+  //
+  // The flow is basically - remote service wishes to (generically) request
+  // interfaces from this service, and so sends us an InterfaceProvider request
+  // (|source_request|) which it would like us to bind. We forward this request
+  // to the Service Manager, passing our actual InterfaceProvider implementation
+  // in |target|. The Service Manager will only forward interface requests that
+  // were permitted by intersecting |source|'s manifest requirements with the
+  // contents of |spec|.
+  ApplySpec(string spec,

[Ken Rockot(use gerrit already), 2017/04/26 04:32:48]

I was kind of thinking we could call specs "interface filters" or "capability
filters". 

Related to but not dependent upon that thought, what about calling this
FilterInterfaces instead of ApplySpec? Then it's a little more clear from the
name what the purpose of the request is.

[Tom Sepez, 2017/04/26 16:22:36]

Yea, SetInterfaceFilter(string filter_name, ... ???

[Ben Goodger (Google), 2017/04/26 17:00:07]

FilterInterfaces sounds fine.

+            Identity source,
+            InterfaceProvider& source_request,
+            InterfaceProvider target);
 };