History log of /frameworks/base/services/core/java/com/android/server/accounts/TokenCache.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c37ee22714ddec1104ba3a2189cf77924ac27812 18-Jun-2015 Carlos Valdivia <carlosvaldivia@google.com> Tweak GET_ACCOUNTS behavior and improve memory.

Related to recent permissions and system health changes. This change
will make it so that calls to AccountManager#getAccountsByType will work
for the owning account authenticator even if they don't have
permissions. This is pretty fundamental to having a working
authenticator and it doesn't make sense to have it be disabled (or have
authenticators hack around the framework).

Also changed how TokenCache works so that memory usage is still
predictable (no more than 64kb) but token caching won't be at the mercy
of garbage collection. This is important for writing stable cts tests.

Change-Id: Ib31b550616b266ee5a04eb26b04ba0023ca0cb83
/frameworks/base/services/core/java/com/android/server/accounts/TokenCache.java
91979be8804232a04da2bf36cdd857ee7da04479 22-May-2015 Carlos Valdivia <carlosvaldivia@google.com> 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
/frameworks/base/services/core/java/com/android/server/accounts/TokenCache.java