diff options
| author | Carlos Valdivia <carlosvaldivia@google.com> | 2015-05-22 14:11:35 -0700 |
|---|---|---|
| committer | Carlos Valdivia <carlosvaldivia@google.com> | 2015-06-02 09:58:18 -0700 |
| commit | 91979be8804232a04da2bf36cdd857ee7da04479 (patch) | |
| tree | 7782f12bc06cfb0b43cc470acc85d7eb966eee3d /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 8fa8b95c9d38183497f08efc6bdf4d2c56a4116c (diff) | |
System Health: Support expiring tokens
In the past android:customTokens=true authenticators were required to handle
their own token caching. This is detrimental for battery when high traffic
authenticators are constantly spinning up processes to start services to do
file io to check their own caches. This change allows authenticator
implementers to optionally let the framework do some of the work for them by
providing the framework with a expiration time.
The AccountManagerService will make a best effort to re-use the cached
token if possible.
Bug: 21530782
Change-Id: I16a7edba36a220e3891e55cf61c725c2be863323
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions