It depends. If you are calling on a proxy for a remote object (or an IBinder that is implemented in native code), the transact() call on that implementation is a native method so you go directly to native code (which then talks with the driver to get the transaction to the other process). This is in the BinderProxy class. Otherwise, you are making a call on a local object which has probably implemented transact() in Java code to unmarshall the data and call the appropriate API on its interface.
On Mon, Jan 5, 2009 at 3:22 PM, martin d. <[email protected]> wrote: > > Hello, > > I am trying to understand some details about how IPC in Android works. > I am stuck at the > point where data is passed from "Java-world" to "native-world" (via > JNI I guess). > > Could someone please tell me, at which point a call to transact() in > Binder.java > gets to native world? Is it android_util_Binder.cpp directly or are > other classes used? > > Hit me with a cluestick, as I am running in circles! > > Thanks, > Martin > > > -- Dianne Hackborn Android framework engineer [email protected] 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-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
