On Wed, Jan 7, 2009 at 10:00 AM, Quartz <[email protected]> wrote:
> currently supported and I am sure ARM would be, eventually, but it > would seem to me that having a sand-boxed native code environment > would be beneficial too. Android already does native sandboxing, as described in the security model doc. That is why I say it would have no purpose for android applications (though it may be useful for its intended purpose in the browser). > I understand the kernel is currently > providing sand-boxing, but the only code you can write is dalvik, at > least from the SDK perspective. I was thinking it would be nice to be > able to code in C or assembly--even if it is a subset--in a sand-boxed > fashion. Adding another sandbox that does the same thing as the existing Android app sandbox is not going to help here. :) -- 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 Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
