WebAPI/WebTelephony/Multi-SIM: Difference between revisions

With various hardware design, there might be multiple ril-daemon (rild), one rild taking care of one SIM, while it is also possible that a single rild manipulates all the SIMs'. To make our architecture flexible enough, we are planning to have 'rilproxy' in charge of sending RIL parcels to the correct rild, no matter how many there are. Moreover, in consideration of code clarity, we introduce multiple instances to achieve one-instance-one-SIM mapping so that we avoid carrying 'the index of SIM slot' in every message.   

Even we create an instance for a SIM, we might still need to add 『index』, used for connecting a telephony object (phoneIndex) and a specific 『sim slot』 due to the limits of the IPC mechanism.