Android Binder 线程池机制详解

连接池代理

我们需要一个代理或工厂接口，根据标识返回对应的 Binder。这是连接池的关键入口。

IBinderPool.aidl

// IBinderPool.aidl
package com.breezehan.ipc.binderpool;

interface IBinderPool {
    IBinder queryBinder(int binderCode);
}

在连接池中实现该接口，根据传入的标识分发不同的 Binder 实例。

static class BinderPoolImpl extends IBinderPool.Stub {
    @Override
    public IBinder queryBinder(int binderCode) throws RemoteException {
        IBinder binder = null;
        switch (binderCode) {
            case BINDER_COMPUTE:
                binder = new ComputeImpl();
                break;
            case BINDER_SECURITY_CENTER:
                binder = new SecurityCenterImpl();
                break;
        }
        return binder;
    }
}

Service 绑定

Service 本身逻辑很简单，主要职责是暴露 BinderPool 接口。

package com.breezehan.ipc.binderpool;

import android.app.Service;
import android.content.Intent;
import android.os.IBinder;
import android.util.Log;

public class BinderPoolService extends Service {
    private static final String TAG = "BinderPoolService";
    private IBinder binderPool = new BinderPool.BinderPoolImpl();

    public BinderPoolService() {}

    @Override
    public IBinder onBind(Intent intent) {
        Log.d(TAG, "onBind");
        return binderPool;
    }

    @Override
    public void onDestroy() {
        super.onDestroy();
    }
}

连接池管理

这部分是核心，负责处理 Service 的连接、单例模式以及 Binder 死亡代理问题。

public class BinderPool {
    private static final String TAG = "BinderPool";
    public static final int BINDER_NONE = -1;
    public static final int BINDER_COMPUTE = 0;
    public static final int BINDER_SECURITY_CENTER = 1;

    private static volatile BinderPool sInstance;
    private final Context mContext;
    // 等待 Service 连接完成的同步工具
    private CountDownLatch mConnectBinderPoolCountDownLatch;
    private IBinderPool mBinderPool;

    public BinderPool(Context context) {
        mContext = context.getApplicationContext();
        connectBinderPoolService();
    }

    private void connectBinderPoolService() {
        mConnectBinderPoolCountDownLatch = new CountDownLatch(1);
        Intent service = new Intent(mContext, BinderPoolService.class);
        mContext.bindService(service, mServiceConnection, Context.BIND_AUTO_CREATE);
        try {
            mConnectBinderPoolCountDownLatch.await();
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
    }

    public static BinderPool getInstance(Context context) {
        if (sInstance == null) {
            synchronized (BinderPool.class) {
                if (sInstance == null) {
                    sInstance = new BinderPool(context);
                }
            }
        }
        return sInstance;
    }

    private ServiceConnection mServiceConnection = new ServiceConnection() {
        @Override
        public void onServiceConnected(ComponentName name, IBinder service) {
            mBinderPool = IBinderPool.Stub.asInterface(service);
            try {
                mBinderPool.asBinder().linkToDeath(mBinderDeathRecipient, 0);
            } catch (RemoteException e) {
                e.printStackTrace();
            }
            mConnectBinderPoolCountDownLatch.countDown();
        }

        @Override
        public void onServiceDisconnected(ComponentName name) {
            // 注意：此回调在服务端崩溃时触发，但无法保证 Binder 状态
        }
    };

    private IBinder.DeathRecipient mBinderDeathRecipient = new IBinder.DeathRecipient() {
        @Override
        public void binderDied() {
            Log.w(TAG, "binderDied: ");
            mBinderPool.asBinder().unlinkToDeath(mBinderDeathRecipient, 0);
            mBinderPool = null;
            // 重连逻辑
            connectBinderPoolService();
        }
    };

    public IBinder queryBinder(int bindCode) {
        IBinder binder = null;
        try {
            binder = mBinderPool.queryBinder(bindCode);
        } catch (RemoteException e) {
            e.printStackTrace();
        }
        return binder;
    }

    static class BinderPoolImpl extends IBinderPool.Stub {
        @Override
        public IBinder queryBinder(int binderCode) throws RemoteException {
            IBinder binder = null;
            switch (binderCode) {
                case BINDER_COMPUTE:
                    binder = new ComputeImpl();
                    break;
                case BINDER_SECURITY_CENTER:
                    binder = new SecurityCenterImpl();
                    break;
            }
            return binder;
        }
    }
}

客户端使用

在 Activity 中模拟调用。这里演示了如何获取 Binder 并进行远程交互。

public class BinderPoolActivity extends AppCompatActivity {
    private static final String TAG = "BinderPoolActivity";

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_binder_pool);
        new Thread(() -> doWork()).start();
    }

    private void doWork() {
        BinderPool pool = BinderPool.getInstance(BinderPoolActivity.this);
        
        // 获取安全中心 Binder
        IBinder securityBinder = pool.queryBinder(BinderPool.BINDER_SECURITY_CENTER);
        ISecurityCenter iSecurityCenter = ISecurityCenter.Stub.asInterface(securityBinder);
        Log.d(TAG, "visit ISecurityCenter");
        String msg = "helloworld-安卓";
        try {
            String encrypt = iSecurityCenter.encrypt(msg);
            Log.d(TAG, "encrypt:" + encrypt);
            Log.d(TAG, "decrypt:" + iSecurityCenter.decrypt(encrypt));
        } catch (RemoteException e) {
            e.printStackTrace();
        }

        // 获取计算服务 Binder
        IBinder computeBinder = pool.queryBinder(BinderPool.BINDER_COMPUTE);
        ICompute iCompute = ICompute.Stub.asInterface(computeBinder);
        try {
            Log.d(TAG, "compute: " + iCompute.add(1, 2));
        } catch (RemoteException e) {
            e.printStackTrace();
        }
    }

    @Override
    protected void onDestroy() {
        super.onDestroy();
    }
}

基本思想如上，如果需要支持更多 Binder，只需在 Switch 语句中添加对应分支即可，扩展性良好。

选择合适的 IPC 方式

每种 IPC 方式都有其优缺点和适用场景，开发者需根据实际需求权衡。

通过对比可以看出，对于需要频繁调用的远程服务，AIDL 配合 Binder 线程池是较为稳健的选择。