diff options
| author | shess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-18 20:34:04 +0000 |
|---|---|---|
| committer | shess@chromium.org <shess@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-18 20:34:04 +0000 |
| commit | c2316134f2d4c02d641e1f0f4ac1e61749313ab4 (patch) | |
| tree | e794f2bc2c97088764d384ab6efe4395acfab46c /gfx/font_unittest.cc | |
| parent | c3a4bd9985658b8a5b229983a3ed85042005f0cf (diff) | |
| download | chromium_src-c2316134f2d4c02d641e1f0f4ac1e61749313ab4.zip chromium_src-c2316134f2d4c02d641e1f0f4ac1e61749313ab4.tar.gz chromium_src-c2316134f2d4c02d641e1f0f4ac1e61749313ab4.tar.bz2 | |
Refactor SafeBrowsingDatabase for transition to new file format.
Refactor old SafeBrowsingDatabase code to allow for transitioning from
the old SQLite-based store to a new SQLite-based store, and from there
to the final raw file-based store.
The intended rollout is:
- Rollout with SafeBrowsingDatabaseBloom (basically the old code).
- Rollout SafeBrowsingDatabase+SafeBrowsingStoreSqlite. This changes
much of the code, but not the file format, so revert is possible
without resync'ing everyone's store (unless the stores have been
corrupted or something).
- Rollout SafeBrowsingDatabase+SafeBrowsingStoreFile. This changes
the file format while the control code stays the same. Revert
requires resync.
- Rollout a big cleanup which removes dead code.
BUG=28647
TEST=Safe browsing continues to work.
Review URL: http://codereview.chromium.org/3141009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56592 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gfx/font_unittest.cc')
0 files changed, 0 insertions, 0 deletions