Some instance came up with the Android security architecture, so it's best 
this instance is responsible for explaining it to the world. This includes 
writing documentation wherever the security architecture's implications leak 
through. It leaks through the Android Framework's Java API, so it should be 
updated accordingly. 

It isn't effective to have the API user community update the documentation, 
as the API user community can only find out via try-and-error whether some 
public method requires a permission.
 
Seeing there is community demand for better permissions documentation, I set 
up Issue 13192 <https://code.google.com/p/android/issues/detail?id=13192>.

-- 
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

Reply via email to