Adds Mojo IDL.

third_party/WebKit/Source/core/mojo/MojoInterfaceProvider.h

+// Copyright 2016 The Chromium Authors. All rights reserved.

[Ken Rockot(use gerrit already), 2016/10/07 23:22:27]

There can be many InterfaceProviders in the system, and InterfaceProvider itself
is just a mojom type with generated bindings.

It might make sense to have some native bindings for exposing various
InterfaceProvider pipes to JS (e.g. mojo.getFrameInterfaceProviderHandle), but
this should only provide a message pipe handle.

You can then use generated JS bindings for InterfaceProvider to bind that handle
to an InterfaceProvider proxy object which will write messages to the pipe.

[alokp, 2016/10/10 16:41:21]

Good idea. In fact it might be more flexible have a dictionary of message-pipe
handles as an attribute on the native binding object.

That said I am trying to keep this API same as the one exposed by gin bindings
so that we can seamlessly transition to this one without changing the code in
mojo/public/js and gin bindings. Once we have transitioned I will make another
cleanup pass. Does that sound reasonable?

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef MojoInterfaceProvider_h
+#define MojoInterfaceProvider_h
+
+#include "bindings/core/v8/ScriptWrappable.h"
+#include "core/CoreExport.h"
+#include "core/mojo/MojoHandle.h"
+#include "public/platform/InterfaceProvider.h"
+#include "wtf/text/WTFString.h"
+
+namespace blink {
+
+class CORE_EXPORT MojoInterfaceProvider
+    : public GarbageCollectedFinalized<MojoInterfaceProvider>,
+      public ScriptWrappable {
+  DEFINE_WRAPPERTYPEINFO();
+
+ public:
+  MojoInterfaceProvider(std::unique_ptr<InterfaceProvider>);
+  virtual ~MojoInterfaceProvider();
+
+  MojoHandle* getInterface(String name);
+
+  DEFINE_INLINE_TRACE() {}
+
+ private:
+  std::unique_ptr<InterfaceProvider> m_provider;
+};
+
+}  // namespace blink
+
+#endif  // MojoInterfaceProvider_h