If you are communicating between activities, you wouldn't use interfaces at all -- all of the communication with be by sending Intents between them in various ways, and you can use Intent.putExtra() to put strings and other data in them.
If you are communicating via a Service, you can use Messenger as the interface returned by onBind(), and you can stuff fairly arbitrary data in the Message with message.setData(). On Wed, Mar 18, 2009 at 9:22 PM, me tun <a...@tpg.com.au> wrote: > > Just say I have two applications, each with one activity running on > separate processes and I want to send a simple string between them. > For the purposes of this example, let us say I have a button that > sends whatever is typed into an EditText view to the other application > where it is then displayed. > > Do I have to expose a remote interface via a service that co-resides > between the two applications? > > Or can I do something simpler (is there a way to pass data between > processes without defining your interface using AIDL)? > > Thanks for clearing this up for me, as I seem to be struggling with > performing IPC at the moment. I'm pretty sure I have to use the > Android IPC path and generate a remote interface using AIDL. I'm just > not sure about the binding to service part. > > Cheers! > > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
