diff options
| author | Makoto Onuki <omakoto@google.com> | 2015-10-13 14:34:03 -0700 |
|---|---|---|
| committer | Makoto Onuki <omakoto@google.com> | 2015-10-27 14:26:06 -0700 |
| commit | 068c54a5be697c3df4657dcda33cd17c4b547710 (patch) | |
| tree | f5e456a5373aa7a8fc9f579918241d6857797a6f /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 7fef1888d16746bc7e154fc04337dc347a512e19 (diff) | |
Layer user restrictions
- Now DPMS remembers user restrictions set by DO / PO in their ActiveAdmin.
- User restrictions set by DO/PO will no longer be saved by UserManger. Instead,
when needed, UMS will consult DPMS to build "effective" user restrictions.
- UM.getUserRestrictions() will now always return "effective" user restrictions.
- DPMS migrates existing user restrictions per the eng spec.
- Also now UM.setUserRestrictions() will crash. UMS.setUserRestrictions() has
been removed.
This was needed because UM.setUserRestrctions(UM.getUserRestrictions()) will no
longer be a valid use like it used to be.
- Also introduced a fined-grained lock for user restrictions in UM to avoid
deadlock between DPMS and also for better performance.
Bug 23902097
Change-Id: If0e1e49344e2f3e9226532d00777976d1eaa7df3
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions