Dart: Adds optional named arguments for creating bindings.

sky/framework/embedder.dart

Index: sky/framework/embedder.dart
diff --git a/sky/framework/embedder.dart b/sky/framework/embedder.dart
index 5c62b7a2f620b5ac77fbc01f38df3f2c6cc89c79..6f70f1b31116e7345e4fbde429293ad988eabf16 100644
--- a/sky/framework/embedder.dart
+++ b/sky/framework/embedder.dart
@@ -26,7 +26,7 @@ class _EmbedderImpl {
       var proxyHandle =
           new core.MojoHandle(internals.takeServicesProvidedByEmbedder());
       _connection = new ApplicationConection(
-          stubHandle.isValid ? new ServiceProviderStub.fromHandle(stubHandle) : null,
+          stubHandle.isValid ? new ServiceProviderBinding.fromHandle(stubHandle) : null,
           proxyHandle.isValid ? new ServiceProviderProxy.fromHandle(proxyHandle) : null);
     }
     return _connection;
@@ -34,9 +34,9 @@ class _EmbedderImpl {
 
   ApplicationConnection connectToApplication(String url) {
     var proxy = new ServiceProviderProxy.unbound();
-    var stub = new ServiceProviderStub.unbound();
-    shell.ptr.connectToApplication(url, proxy, stub);
-    return new ApplicationConnection(stub, proxy);
+    var binding = new ServiceProviderBinding.unbound();

[hansmuller1, 2015/03/02 20:42:18]

Calling the stub class a "binding" has its merits. On the other hand, it's odd
that a FooProxy can be created "unbound", since "unbound" seems to go with
FooBinding.

It's also odd that you can don't bind a Binding (as you can in C++), you set its
implementation delegate.

I'm not really objecting to any of this, although personally I found it easier
to understand the way it was.

+    shell.ptr.connectToApplication(url, proxy, binding);
+    return new ApplicationConnection(binding, proxy);
   }
 
   void connectToService(String url, bindings.ProxyBase proxy) {