IdentityManager: Remove caching of accounts with refresh tokens
This CL streamlines IdentityManager's interaction with AccountTrackerService when firing updates for accounts with refresh tokens. Rather than caching state locally in response to PO2TS::DiagnosticsClient callbacks, IdentityManager simply obtains the AccountInfo from AccountTracker in the PO2TS observer callback itself. This CL eliminates the need for any cached state in IdentityManager related to accounts with refresh tokens. The motivation is to enable conversion of the codebase to IdentityManager as smoothly and painlessly as possible, as explained in detail in crbug.com/883722. Bug: 883722 Change-Id: Ic13d5be5a5f17411c167d19da7f8444e6ec257bc Reviewed-on: https://chromium-review.googlesource.com/1228197 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#593142}
Showing
Please register or sign in to comment