What are the IPC mechanisms available in the Android OS?

AndroidAndroid IntentIpcAndroid BundleAndroid Binder

Android Problem Overview


Will any one please tell me what are all the IPC mechanisms that are present in Android.

To my knowledge are:

  1. Intents
  2. Binders

Android Solutions


Solution 1 - Android

IPC is inter-process communication. It describes the mechanisms used by different types of android components to communicate with one another.

  1. Intents are messages which components can send and receive. It is a universal mechanism of passing data between processes. With help of the intents one can start services or activities, invoke broadcast receivers and so on.

  2. Bundles are entities of data that is passed through. It is similar to the serialization of an object, but much faster on android. Bundle can be read from intent via the getExtras() method.

  3. Binders are the entities which allow activities and services to obtain a reference to another service. It allows not simply sending messages to services but directly invoking methods on them.

Solution 2 - Android

There are three types of IPC mechanism in Android:

  1. Intents (along with Bundles)
  2. Binders
  3. ASHMEM (Anonymous Shared Memory) - The main difference between Linux shared memory and this shared memory is, in Linux other processes can't free the shared memory but here if other processes require memory this memory can be freed by Android OS.

Solution 3 - Android

All the answers are good and concise in this post. But I would like to light upon which IPC mechanism should we use. First of all IPC means Inter Process communication where two applications or processes will communicate with each other by passing some data between them. Since android is meant for embedded and small devices, we should not use serialization for IPC, rather we can use BINDERs which internally uses parcels. Parcel is a sort of light weight serialization by using shared memory concept.

There are many differences between Binder IPC and Serialization IPC:

1. Serialization is very heavy to use in embedded devices, communication will be very slow.

2. Binders uses Parcels to make IPC very fast.

3. Binders internally uses Shared memory concept which uses less memory while sharing data between two processes.

Bottom Line: Binders uses less memory, and quite fast as it uses parcels. Serialization is very heavy, takes time to send and receive data, and also it takes more memory compared to binders.

Note: To pass data between activities, services, and receivers use only Bundles. Don't go for either serialization or binders. Binders are specifically used only for binder services where 2 processes will communicate.

Hope this Helps :)

Solution 4 - Android

As written on Android Developers page, IPC mechanisms in Android include:

  • Intents (with Bundles included)
  • Binders or Messengers with a Service
  • BroadcastReceivers

Solution 5 - Android

There are three types of the IPC mechanisms:

  1. handler
  2. implementing binder
  3. AIDL

Solution 6 - Android

The tree specific inter-process communications in Android are:

  1. AIDL which is a two way with concurrent operation.
  2. Messanger aa a two way but not concurrent
  3. Broadcast as a one way Also, you can use sockets but it's not recommended.

Solution 7 - Android

Another solution that worked for me was using the Internal files:

https://developer.android.com/training/data-storage#filesInternal

Write from one process, close file, read from another.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSumanView Question on Stackoverflow
Solution 1 - AndroidVladimir IvanovView Answer on Stackoverflow
Solution 2 - AndroidSumanView Answer on Stackoverflow
Solution 3 - AndroidSetu Kumar BasakView Answer on Stackoverflow
Solution 4 - AndroidlomzaView Answer on Stackoverflow
Solution 5 - AndroidswapView Answer on Stackoverflow
Solution 6 - AndroidmhheydarchiView Answer on Stackoverflow
Solution 7 - AndroidRaul LucaciuView Answer on Stackoverflow