Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(4)

Side by Side Diff: sync/syncable/in_memory_directory_backing_store.h

Issue 9699057: [Sync] Move 'sync' target to sync/ (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Fix some minor diffs Created 8 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 // Copyright (c) 2012 The Chromium Authors. All rights reserved. 1 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 #ifndef CHROME_BROWSER_SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ 5 #ifndef SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_
tim (not reviewing) 2012/03/15 06:21:10 curious... if this is test only, why isn't it part
akalin 2012/03/15 07:38:26 Well, it's pulled into production code (from synca
6 #define CHROME_BROWSER_SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ 6 #define SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_
7 #pragma once 7 #pragma once
8 8
9 #include "chrome/browser/sync/syncable/directory_backing_store.h" 9 #include "sync/syncable/directory_backing_store.h"
10 10
11 namespace syncable { 11 namespace syncable {
12 12
13 // This implementation of DirectoryBackingStore is used in tests that do not 13 // This implementation of DirectoryBackingStore is used in tests that do not
14 // require us to write to a file. An in-memory sqlite database is much faster 14 // require us to write to a file. An in-memory sqlite database is much faster
15 // than an on-disk database, so this can result in significant speedups in our 15 // than an on-disk database, so this can result in significant speedups in our
16 // unit tests. 16 // unit tests.
17 // 17 //
18 // An InMemoryDirectoryBackingStore cannot load data from existing databases. 18 // An InMemoryDirectoryBackingStore cannot load data from existing databases.
19 // When an InMemoryDirectoryBackingStore is destroyed, all data stored in this 19 // When an InMemoryDirectoryBackingStore is destroyed, all data stored in this
20 // database is lost. If these limitations are a problem for you, consider using 20 // database is lost. If these limitations are a problem for you, consider using
21 // TestDirectoryBackingStore. 21 // TestDirectoryBackingStore.
22 class InMemoryDirectoryBackingStore : public DirectoryBackingStore { 22 class InMemoryDirectoryBackingStore : public DirectoryBackingStore {
23 public: 23 public:
24 explicit InMemoryDirectoryBackingStore(const std::string& dir_name); 24 explicit InMemoryDirectoryBackingStore(const std::string& dir_name);
25 virtual DirOpenResult Load( 25 virtual DirOpenResult Load(
26 MetahandlesIndex* entry_bucket, 26 MetahandlesIndex* entry_bucket,
27 Directory::KernelLoadInfo* kernel_load_info) OVERRIDE; 27 Directory::KernelLoadInfo* kernel_load_info) OVERRIDE;
28 }; 28 };
29 29
30 } // namespace syncable 30 } // namespace syncable
31 31
32 #endif // CHROME_BROWSER_SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ 32 #endif // SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698