Re: Binder documentation - RFC/peer review
Hi Devi, Can you also throw some light on how the IBinder interface is connected to the aidl files? When you define an abstract method in an aidl file, you can specify if the parameter is an input parameter or an output parameter. I was looking around for examples which contain an out parameter just to understand where the memory is allocated for this parameter. But I haven't found any. It will great if you can extend your document to cover that region too. Thank you, Naveen On Jul 19, 9:01 pm, devi prasad dpras...@gmail.com wrote: Hi, Dianne - thanks for the encouraging words! I've seen dump() getting used for the debugging purpose you mentioned. I'll certainly mention it in the upcoming draft. That said, I also see a use that I have mentioned; after all, it is declared pure virtual and so we may as well want our components to serialize themselves to a stream when required. This will fit into the scheme I was mentioning in the document - services that pool objects if they are not pinged for a period of time. thanks anyway. I'll keep working in my spare time! On Mon, Jul 20, 2009 at 2:28 AM, Dianne Hackbornhack...@android.com wrote: Hi, nice job! One small comment -- the dump() method actually for debugging. An object can implement by printing interesting parts of its current state as text to the output stream. In particular, this is what makes the dumpsys command work -- all dumpsys really does is call dump() on whatever IBinder objects it wants to print. On Sun, Jul 19, 2009 at 3:12 AM, devi prasad dpras...@gmail.com wrote: Hi, I'm preparing a document describing Binder implementation in Android. I've already written about four pages combining how-to-write-a-binder-program with how-does-it-work style of writing. As I progressed, I thought it might be useful to listen to what others think about such an approach. So I'm attaching the document for your comments. Please take a look at it and provide your suggestions, opinions, views, and what not, to make this a useful document. FYI, English is not my mother tongue. Therefore, my style may not be smooth on ears that converse in English :-) Please feel free to suggest improvements not only on the content but also on the overall style and readability. Thank you for your time and patience Devi Prasad PS: I've posted this on both platform and framework groups. I'm always confused about these two forums ;-) -- 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, and so won't reply to such e-mails. 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 android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~--~~~~--~~--~--~---
Re: Binder documentation - RFC/peer review
Hi, Naveen - thanks for your interest. I'll definitely address your questions too! I want to complete this soon. But my day job doesn't let me do binder documentation :) I need to squeeze this in the time I find, which I definitely will! On Mon, Jul 20, 2009 at 7:42 PM, Naveen Knaveen...@gmail.com wrote: Hi Devi, Can you also throw some light on how the IBinder interface is connected to the aidl files? When you define an abstract method in an aidl file, you can specify if the parameter is an input parameter or an output parameter. I was looking around for examples which contain an out parameter just to understand where the memory is allocated for this parameter. But I haven't found any. It will great if you can extend your document to cover that region too. Thank you, Naveen On Jul 19, 9:01 pm, devi prasad dpras...@gmail.com wrote: Hi, Dianne - thanks for the encouraging words! I've seen dump() getting used for the debugging purpose you mentioned. I'll certainly mention it in the upcoming draft. That said, I also see a use that I have mentioned; after all, it is declared pure virtual and so we may as well want our components to serialize themselves to a stream when required. This will fit into the scheme I was mentioning in the document - services that pool objects if they are not pinged for a period of time. thanks anyway. I'll keep working in my spare time! On Mon, Jul 20, 2009 at 2:28 AM, Dianne Hackbornhack...@android.com wrote: Hi, nice job! One small comment -- the dump() method actually for debugging. An object can implement by printing interesting parts of its current state as text to the output stream. In particular, this is what makes the dumpsys command work -- all dumpsys really does is call dump() on whatever IBinder objects it wants to print. On Sun, Jul 19, 2009 at 3:12 AM, devi prasad dpras...@gmail.com wrote: Hi, I'm preparing a document describing Binder implementation in Android. I've already written about four pages combining how-to-write-a-binder-program with how-does-it-work style of writing. As I progressed, I thought it might be useful to listen to what others think about such an approach. So I'm attaching the document for your comments. Please take a look at it and provide your suggestions, opinions, views, and what not, to make this a useful document. FYI, English is not my mother tongue. Therefore, my style may not be smooth on ears that converse in English :-) Please feel free to suggest improvements not only on the content but also on the overall style and readability. Thank you for your time and patience Devi Prasad PS: I've posted this on both platform and framework groups. I'm always confused about these two forums ;-) -- 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, and so won't reply to such e-mails. 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 android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~--~~~~--~~--~--~---
Re: Binder documentation - RFC/peer review
I received a couple emails pointing out that the document in incomplete. Please note that this document is unfinished and therefore incomplete, as it stands now. I'm presenting this (draft, incomplete document) to the group just to hear the views of others who may convince me to change the presentation style. thanks Devi Prasad On Sun, Jul 19, 2009 at 3:42 PM, devi prasaddpras...@gmail.com wrote: Hi, I'm preparing a document describing Binder implementation in Android. I've already written about four pages combining how-to-write-a-binder-program with how-does-it-work style of writing. As I progressed, I thought it might be useful to listen to what others think about such an approach. So I'm attaching the document for your comments. Please take a look at it and provide your suggestions, opinions, views, and what not, to make this a useful document. FYI, English is not my mother tongue. Therefore, my style may not be smooth on ears that converse in English :-) Please feel free to suggest improvements not only on the content but also on the overall style and readability. Thank you for your time and patience Devi Prasad PS: I've posted this on both platform and framework groups. I'm always confused about these two forums ;-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups android-framework group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~--~~~~--~~--~--~---
Re: Binder documentation - RFC/peer review
Hi, nice job! One small comment -- the dump() method actually for debugging. An object can implement by printing interesting parts of its current state as text to the output stream. In particular, this is what makes the dumpsys command work -- all dumpsys really does is call dump() on whatever IBinder objects it wants to print. On Sun, Jul 19, 2009 at 3:12 AM, devi prasad dpras...@gmail.com wrote: Hi, I'm preparing a document describing Binder implementation in Android. I've already written about four pages combining how-to-write-a-binder-program with how-does-it-work style of writing. As I progressed, I thought it might be useful to listen to what others think about such an approach. So I'm attaching the document for your comments. Please take a look at it and provide your suggestions, opinions, views, and what not, to make this a useful document. FYI, English is not my mother tongue. Therefore, my style may not be smooth on ears that converse in English :-) Please feel free to suggest improvements not only on the content but also on the overall style and readability. Thank you for your time and patience Devi Prasad PS: I've posted this on both platform and framework groups. I'm always confused about these two forums ;-) -- 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, and so won't reply to such e-mails. 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 android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~--~~~~--~~--~--~---
Re: Binder documentation - RFC/peer review
Hi, Dianne - thanks for the encouraging words! I've seen dump() getting used for the debugging purpose you mentioned. I'll certainly mention it in the upcoming draft. That said, I also see a use that I have mentioned; after all, it is declared pure virtual and so we may as well want our components to serialize themselves to a stream when required. This will fit into the scheme I was mentioning in the document - services that pool objects if they are not pinged for a period of time. thanks anyway. I'll keep working in my spare time! On Mon, Jul 20, 2009 at 2:28 AM, Dianne Hackbornhack...@android.com wrote: Hi, nice job! One small comment -- the dump() method actually for debugging. An object can implement by printing interesting parts of its current state as text to the output stream. In particular, this is what makes the dumpsys command work -- all dumpsys really does is call dump() on whatever IBinder objects it wants to print. On Sun, Jul 19, 2009 at 3:12 AM, devi prasad dpras...@gmail.com wrote: Hi, I'm preparing a document describing Binder implementation in Android. I've already written about four pages combining how-to-write-a-binder-program with how-does-it-work style of writing. As I progressed, I thought it might be useful to listen to what others think about such an approach. So I'm attaching the document for your comments. Please take a look at it and provide your suggestions, opinions, views, and what not, to make this a useful document. FYI, English is not my mother tongue. Therefore, my style may not be smooth on ears that converse in English :-) Please feel free to suggest improvements not only on the content but also on the overall style and readability. Thank you for your time and patience Devi Prasad PS: I've posted this on both platform and framework groups. I'm always confused about these two forums ;-) -- 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, and so won't reply to such e-mails. 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 android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~--~~~~--~~--~--~---
