On Wed, Jun 13, 2012 at 1:33 AM, michael <[email protected]> wrote: > Hi, > > the following is one statement, is it correct? : > that applications do not run natively and inter-app communications > must take place via IPC is not entirely true. There are ways for > application to communicate without going through pre-defined OS > provided channels. > > > Thanks a lot for your reply > > M >
There are lots of ways for apps to communicate: -- Intents, -- Content providers, -- Direct RPC a la AIDL, -- Writing to a shared file, -- etc..., the list goes on. By far, the most common paradigms are using either intents, or RPC (either with AIDL or a Messenger, which is built on top of AIDL). Using intents are a fairly lightweight asynchronous communication mechanism, though their expressiveness is somewhat limited, whereas direct RPC ties the apps together more, and you might not need it if you're sending simple messages. Your statement doesn't make any sense, by the way. Whether apps run naively or not depends on the vm implementation. They definitely run on top of the vm, as everything in Android does, but they may or may not be run in compiled code via JIT. They have to communicate using the mechanisms provided., but as I said there's a wide range of things possible, even using ashmem, http://www.androidenea.com/2010/03/share-memory-using-ashmem-and-binder-in.html kris kris -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
