It's as efficient as sending a message. If you are going across processes, the field is dropped; if going in-process, it is just the same message object, so there is no extra work.
On Mar 25, 10:46 am, "Harsh Jain" <[EMAIL PROTECTED]> wrote: > Its not going across processes. Its going to the handler from one of the > threads invoking service. I got it working, but I had still like to know if > this is efficient ? > > regards, > harsh > > On Tue, Mar 25, 2008 at 10:05 PM, hackbod <[EMAIL PROTECTED]> wrote: > > > A generic object can't be marshalled across processes, so if the call > > is going across processes, this field will be null. You'll need to > > put the data in the extras map in a form that can be marshalled. > > > On Mar 25, 7:14 am, "Harsh Jain" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I created a local class, with one of the member being an AIDL declared > > > callback interface. I am trying to pass instances of this class using > > > Message.obj field to the handler, so that he can execute the callback. > > But > > > it doesnt seem to work, The message.obj becomes null in the handler > > code. > > > Please advice. > > > > regards, > > > harsh --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
