recently, a set of APP,APP internal data is shared on a customized machine. If I want to do a set of internal communication between APP processes, I used aidl at first and found that aidl is easy to disconnect in the case of multiple concurrency. And it is easy to wait for a connection when it is started for the first time.
several options have been considered at present, but I don"t know which one is better.
1. Reencapsulate the aidl and write a separate APP to process the aidl. All other APP are summed up to this APP for processing, solving the problem of multi-concurrent disconnection. But it will certainly be less efficient.
2. Use ele.me encapsulated HermesEventBus to deal with, this is the packaged aidl framework. Not yet in use, I don"t know if it works, and I don"t know if it can solve the problem of multiple concurrency!
3. Re-encapsulated with tcp, the bottom layer of aidl is the implementation of Binder,Binder is the protocol layer of tcp/ip, so I want to use tcp to do a set of process communication mechanism, I do not know whether it is feasible. The solution that comes to mind now is using tcp (mina/netty) nio.
are these options feasible, and are there any new solutions?