On Tue, Aug 9, 2011 at 11:53 AM, Chris Stratton <[email protected]> wrote: > Unlikely, as it can be done with the ndk, and we are repeatedly told that > the ndk does not have special permissions. Most likely they just didn't > bother implementing support in javaj for something that wasn't envisioned as > needed.
Possibly, but I'm skeptical. Bear in mind that the decision to remove those methods was made years before the NDK existed. > However, on internal storage where permissions matter, the java file > creation tools do let you set the permissions to some extent (ie, various > android presets, but not full unix bit-level control) Very true. > Ordinary files owned by an application user id and residing on a filesystem > where it is meaningful can however have their permission bits changed. That being said, IMHO it's rarely a good idea. I would rather developers provide a real API (remote service, content provider, etc.). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- 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
