diff options
author | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-22 19:50:31 +0000 |
---|---|---|
committer | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-22 19:50:31 +0000 |
commit | e2fc3d25fe020a7e7518af1aea31085adc1002a1 (patch) | |
tree | fc64854da0b8cc3ac30df1bb6a399885365fb092 /chrome/browser/browser_uitest.cc | |
parent | f09ef6740a2d3342dd41796e01916957d20b6586 (diff) | |
download | chromium_src-e2fc3d25fe020a7e7518af1aea31085adc1002a1.zip chromium_src-e2fc3d25fe020a7e7518af1aea31085adc1002a1.tar.gz chromium_src-e2fc3d25fe020a7e7518af1aea31085adc1002a1.tar.bz2 |
Fix appcache_service and request_context referencing.
There is one appcache service per profile and several request context per profile. The profile holds a reference to the appcache service. Those request contexts which are subject to retrieval from appcaches hold a reference to the appcache service too. The appcache service is provided with a pointer back to the 'main' request context, this context is used when updating appcaches.
Initialization is a little tricky because profiles can't be used on the IO thread and request contexts can't be used on the UI thread.
BUG=22597,22125
TEST=many existing tests exercise profile/context creation
Review URL: http://codereview.chromium.org/215024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26844 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser_uitest.cc')
0 files changed, 0 insertions, 0 deletions