Refactoring ChildProcessConnection.

content/public/android/java/src/org/chromium/content/browser/BindingManager.java

 // 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.
 
 package org.chromium.content.browser;
 
 import android.content.Context;
 
 /**
  * Manages oom bindings used to bound child services. "Oom binding" is a binding that raises the
@@ skipping 14 matching lines @@
  *   background
  *
  * Thread-safety: most of the methods will be called only on the main thread, exceptions are
  * explicitly noted.
  */
 public interface BindingManager {
     /**
      * Registers a freshly started child process. This can be called on any thread.
      * @param pid handle of the service process
      */
-    void addNewConnection(int pid, ChildProcessConnection connection);
+    void addNewConnection(int pid, ManagedChildProcessConnection connection);
 
     /**
      * Called when the service visibility changes or is determined for the first time. On low-memory
      * devices this will also drop the oom bindings of the last process that was oom-bound if a new
      * process is used in foreground.
      * @param pid handle of the service process
      * @param inForeground true iff the service is visibile to the user
      */
     void setInForeground(int pid, boolean inForeground);
 
@@ skipping 17 matching lines @@
 
     /**
      * Called when the embedding application is brought to foreground. This will drop the strong
      * binding kept on the main renderer during the background period, so the embedder should make
      * sure that this is called after the regular strong binding is attached for the foreground
      * session.
      */
     void onBroughtToForeground();
 
     /**
-     * @return True iff the given service process is protected from the out-of-memory killing, or it
-     * was protected when it died unexpectedly. This can be used to decide if a disconnection of a
-     * renderer was a crash or a probable out-of-memory kill. This can be called on any thread.
-     */
-    boolean isOomProtected(int pid);
-
-    /**
      * Should be called when the connection to the child process goes away (either after a clean
      * exit or an unexpected crash). At this point we let go of the reference to the
      * ChildProcessConnection. This can be called on any thread.
      */
-    void clearConnection(int pid);
+    void removeConnection(int pid);
 
     /**
      * Starts moderate binding management.
      * Please see https://goo.gl/tl9MQm for details.
      */
     void startModerateBindingManagement(Context context, int maxSize);
 
     /**
      * Releases all moderate bindings.
      */
     void releaseAllModerateBindings();
 }