I guess. Runtime is fundamentally "on the side". Think of runtime as the CPU for code written in Java: apps use the runtime directly, java framework libraries use the runtime directly. Diagram would be better if runtime went to top all the way.
JNI allows to go directly from application framework to libraries without going through runtime. Runtime doesn't work directly with kernel (would be very unusual), probably goes through libc, kernel interface is specific to CPU and not portable. On Mar 26, 6:59 am, szeldon <[EMAIL PROTECTED]> wrote: > Hi, > > My question is a little silly one, but I wonder why on diagram > athttp://code.google.com/android/what-is-android.html > the Android Runtime layer is not between Application Framework and > Libraries? Is this because Android Runtime uses kernel's functionality > for threading and low-level memory management? So why this Runtime > layer is not "touching" the Linux Kernel on this diagram? Don't get me > wrong, I'm not trying to critisize this. I think docs are great there > but I think that this could help me understand how the virtual machine > works. --~--~---------~--~----~------------~-------~--~----~ 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 [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 -~----------~----~----~----~------~----~------~--~---
