Remove ShellConnection::WaitForInitialize

This changes ShellClient::Initialize to expect a
response with an optional Connector request rather
than a ConnectorPtr being passed in with the call.
This allows clients to create their own Connector
pipe and lazily connect it to the shell thus
avoiding any practical need to wait for an
Initialize message.

Additionally:

 - Client instances no longer die on the first
   Connector pipe error: instead an Instance is
   kept alive by the shell as long as either the
   ShellClient pipe is connected OR any Connector
   pipes are connected.

 - ShellClientFactory endpoints are now strongly
   typed instead of being raw message pipe
   handles.

 - Some uses of MessagePumpMojo near other changes
   in this CL have been opportunistically removed.

BUG=591742

Review URL: https://codereview.chromium.org/1793793002

Cr-Commit-Position: refs/heads/master@{#380909}

1 files changed, 4 insertions, 0 deletions

diff --git a/mojo/edk/embedder/embedder.h b/mojo/edk/embedder/embedder.h
index 99191a9..b96d847 100644
--- a/mojo/edk/embedder/embedder.h
+++ b/mojo/edk/embedder/embedder.h
@@ -48,6 +48,10 @@ MOJO_SYSTEM_IMPL_EXPORT void ChildProcessLaunched(
 // that the parent received from ChildProcessLaunched.
 MOJO_SYSTEM_IMPL_EXPORT void SetParentPipeHandle(ScopedPlatformHandle pipe);
 
+// Same as above but extracts the pipe handle from the command line. See
+// PlatformChannelPair for details.
+MOJO_SYSTEM_IMPL_EXPORT void SetParentPipeHandleFromCommandLine();
+
 // Must be called first, or just after setting configuration parameters, to
 // initialize the (global, singleton) system.
 MOJO_SYSTEM_IMPL_EXPORT void Init();