Add different behavior to AwakableList for "persistent" vs "one-shot" awakables.

mojo/edk/system/message_pipe.cc

 // Copyright 2013 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 "mojo/edk/system/message_pipe.h"
 
 #include <memory>
 #include <utility>
 
 #include "base/logging.h"
@@ skipping 174 matching lines @@
 
   MutexLocker locker(&mutex_);
   DCHECK(endpoints_[port]);
 
   return endpoints_[port]->GetHandleSignalsState();
 }
 
 MojoResult MessagePipe::AddAwakable(unsigned port,
                                     Awakable* awakable,
                                     uint64_t context,
-                                    bool force,
+                                    bool persistent,
                                     MojoHandleSignals signals,
                                     HandleSignalsState* signals_state) {
   DCHECK(port == 0 || port == 1);
 
   MutexLocker locker(&mutex_);
   DCHECK(endpoints_[port]);
 
-  return endpoints_[port]->AddAwakable(awakable, context, force, signals,
+  return endpoints_[port]->AddAwakable(awakable, context, persistent, signals,
                                        signals_state);
 }
 
 void MessagePipe::RemoveAwakable(unsigned port,
                                  bool match_context,
                                  Awakable* awakable,
                                  uint64_t context,
                                  HandleSignalsState* signals_state) {
   DCHECK(port == 0 || port == 1);
 
@@ skipping 160 matching lines @@
       LOG(WARNING) << "Enqueueing null dispatcher";
       handles->push_back(Handle());
     }
   }
   message->SetHandles(std::move(handles));
   return MOJO_RESULT_OK;
 }
 
 }  // namespace system
 }  // namespace mojo