summaryrefslogtreecommitdiffstats
path: root/chrome/browser/autofill/form_group.cc
diff options
context:
space:
mode:
authorsky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-27 15:22:54 +0000
committersky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-27 15:22:54 +0000
commit809cc4d808f30112929ef9c33183e6cc052d3f88 (patch)
tree54398a78a324c611c7413d386d62aad68c01b17b /chrome/browser/autofill/form_group.cc
parent68d5a677812099c0d85b1c22f9234e8db9ddfc03 (diff)
downloadchromium_src-809cc4d808f30112929ef9c33183e6cc052d3f88.zip
chromium_src-809cc4d808f30112929ef9c33183e6cc052d3f88.tar.gz
chromium_src-809cc4d808f30112929ef9c33183e6cc052d3f88.tar.bz2
Attempt 2 at landing top sites refactor:
Refactors TopSites so that it's hopefully easier to maintain and doesn't suffer the plethora of threading issues that exist with the current version. Here's the breakdown of what was refactored: . TopSitesCache: Contains the most visited urls and thumbnails. . TopSitesBackend: All mutations to topsites data end up calling into the backend on the UI thread. TopSitesBackend processes the method on the DB thread calling through to the TopSitesDatabase. . TopSites: uses two TopSitesCache. One that contains the raw history data, the other contains the processed data (pinned/blacklisted). The processed cache can be accessed on any thread. TopSites waits until history loads to know if it should migrate or use it's own db. I could probably make these execute in parallel, but for now this is how it works. This patch also makes it so the dom ui accesses the thumbnails on the IO thread. BUG=56382 TEST=Make sure all your thumbnails are correctly updated and you don't see problems. Review URL: http://codereview.chromium.org/4051004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64072 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/autofill/form_group.cc')
0 files changed, 0 insertions, 0 deletions