diff options
| author | Steve Block <steveblock@google.com> | 2010-10-27 11:29:59 +0100 |
|---|---|---|
| committer | Steve Block <steveblock@google.com> | 2010-10-27 14:07:30 +0100 |
| commit | 43d943757c6b39710fa65034351bc2e84946e8ce (patch) | |
| tree | a16a463e91d132c5d94ea0d933d90f8fd9c4fab2 /WebKit/android/nav | |
| parent | 9a90c4fd9e9ad727fac52b12013ad2b88644d826 (diff) | |
| download | external_webkit-43d943757c6b39710fa65034351bc2e84946e8ce.zip external_webkit-43d943757c6b39710fa65034351bc2e84946e8ce.tar.gz external_webkit-43d943757c6b39710fa65034351bc2e84946e8ce.tar.bz2 | |
Update Chromium HTTP stack to get database and cache paths from CookieSyncManager
Currently these paths are obtained from the BrowserFrame via JNI.
However, the paths are not synced to the BrowserFrame until the
WebCore thread has started up. This means that if the
WebRequestContext is created on the IO thread, the paths may not be
available.
This change moves the paths from BrowserFrame to CookieSyncManager to
avoid the need to wait for the WebCore thread.
Note that the new methods may be called on either the UI or WebCore
threads, so are synchronised.
Requires a change to frameworks/base ...
https://android-git.corp.google.com/g/76580
Change-Id: I61f88772d13901d66892118c79db3cac412e6bd1
Diffstat (limited to 'WebKit/android/nav')
0 files changed, 0 insertions, 0 deletions