Mojo EDK: Add safe process connection API

content/common/service_manager/child_connection.cc

 // Copyright 2015 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.
 
 #include "content/common/service_manager/child_connection.h"
 
 #include <stdint.h>
 #include <utility>
 
 #include "base/macros.h"
@@ skipping 105 matching lines @@
   scoped_refptr<base::SequencedTaskRunner> io_task_runner_;
   std::unique_ptr<service_manager::Connection> connection_;
   service_manager::mojom::PIDReceiverPtr pid_receiver_;
 
   DISALLOW_COPY_AND_ASSIGN(IOThreadContext);
 };
 
 ChildConnection::ChildConnection(
     const std::string& service_name,
     const std::string& instance_id,
-    const std::string& child_token,
+    const mojo::edk::PendingProcessConnection& process_connection,
     service_manager::Connector* connector,
     scoped_refptr<base::SequencedTaskRunner> io_task_runner)
-    : child_token_(child_token),
-      context_(new IOThreadContext),
+    : context_(new IOThreadContext),
       child_identity_(service_name,
                       service_manager::mojom::kInheritUserID,
                       instance_id),
-      service_token_(mojo::edk::GenerateRandomToken()),
       weak_factory_(this) {
-  mojo::ScopedMessagePipeHandle service_pipe =
-      mojo::edk::CreateParentMessagePipe(service_token_, child_token_);
-
-  context_->Initialize(child_identity_, connector, std::move(service_pipe),
+  context_->Initialize(child_identity_, connector,
+                       process_connection.CreateMessagePipe(&service_token_),
                        io_task_runner);
   remote_interfaces_.Forward(
       base::Bind(&CallBinderOnTaskRunner,
                  base::Bind(&IOThreadContext::GetRemoteInterfaceOnIOThread,
                             context_), io_task_runner));
 }
 
 ChildConnection::~ChildConnection() {
   context_->ShutDown();
-
-  if (process_handle_ == base::kNullProcessHandle) {
-    // The process handle was never set, so we have to assume the process was
-    // not successfully launched. Note that ChildProcessLauncher may also call
-    // call ChildProcessLaunchFailed for the same token, so this is (harmlessly)
-    // redundant in some cases.
-    mojo::edk::ChildProcessLaunchFailed(child_token_);
-  }
 }
 
 void ChildConnection::SetProcessHandle(base::ProcessHandle handle) {
   process_handle_ = handle;
   context_->SetProcessHandle(handle);
 }
 
 }  // namespace content