diff options
| author | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-24 03:54:41 +0000 |
|---|---|---|
| committer | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-24 03:54:41 +0000 |
| commit | 9843f19b5da27c85fb8a9ce22521256de6ec7da1 (patch) | |
| tree | b59c86a84361e24ce94cdbefc20851d6ffba34a5 /chrome/browser/chromeos/drive/resource_metadata_storage_unittest.cc | |
| parent | 44d1808913703cc78bbed25d11263358ee1f59b7 (diff) | |
| download | chromium_src-9843f19b5da27c85fb8a9ce22521256de6ec7da1.zip chromium_src-9843f19b5da27c85fb8a9ce22521256de6ec7da1.tar.gz chromium_src-9843f19b5da27c85fb8a9ce22521256de6ec7da1.tar.bz2 | |
settings: Make DeviceOAuth2TokenServiceFactory::Get() async
This is in preparation for fixing nasty D-Bus method call issues in
DeviceOAuth2TokenService.
In crrev.com/228189, we had to add horrible hacks to workaround an urgent
P1 issue, which needed to be merged to M31 branch immediately.
The root cause of this problem is the fact that DeviceOAuth2TokenService
issues D-Bus method calls, which should be asynchronous, from places
where doing it asynchronously is difficult (in particular, making
GetRefreshToken() asynchronous is very difficult: crbug.com/309952).
A simpler solution for this problem is to get the system salt before
creating DeviceOAuth2TokenService, hence Get() should be asynchronous.
BUG=309959,306547
TEST=none
R=courage@chromium.org, hashimoto@chromium.org, pastarmovj@chromium.org, pneubeck@chromium.org, xiyuan@chromium.org
Review URL: https://codereview.chromium.org/34523003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230624 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/chromeos/drive/resource_metadata_storage_unittest.cc')
0 files changed, 0 insertions, 0 deletions