OLD | NEW |
1 // Copyright 2012 The Chromium Authors. All rights reserved. | 1 // Copyright 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 SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ | 5 #ifndef SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ |
6 #define SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ | 6 #define SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ |
7 | 7 |
8 #include <string> | 8 #include <string> |
9 | 9 |
| 10 #include "base/macros.h" |
| 11 #include "sync/base/sync_export.h" |
10 #include "sync/syncable/directory_backing_store.h" | 12 #include "sync/syncable/directory_backing_store.h" |
11 #include "sync/base/sync_export.h" | |
12 | 13 |
13 namespace syncer { | 14 namespace syncer { |
14 namespace syncable { | 15 namespace syncable { |
15 | 16 |
16 // This implementation of DirectoryBackingStore is used in tests that do not | 17 // This implementation of DirectoryBackingStore is used in tests that do not |
17 // require us to write to a file. An in-memory sqlite database is much faster | 18 // require us to write to a file. An in-memory sqlite database is much faster |
18 // than an on-disk database, so this can result in significant speedups in our | 19 // than an on-disk database, so this can result in significant speedups in our |
19 // unit tests. | 20 // unit tests. |
20 // | 21 // |
21 // An InMemoryDirectoryBackingStore cannot load data from existing databases. | 22 // An InMemoryDirectoryBackingStore cannot load data from existing databases. |
22 // When an InMemoryDirectoryBackingStore is destroyed, all data stored in this | 23 // When an InMemoryDirectoryBackingStore is destroyed, all data stored in this |
23 // database is lost. If these limitations are a problem for you, consider using | 24 // database is lost. If these limitations are a problem for you, consider using |
24 // TestDirectoryBackingStore. | 25 // TestDirectoryBackingStore. |
25 class SYNC_EXPORT InMemoryDirectoryBackingStore : public DirectoryBackingStore { | 26 class SYNC_EXPORT InMemoryDirectoryBackingStore : public DirectoryBackingStore { |
26 public: | 27 public: |
27 explicit InMemoryDirectoryBackingStore(const std::string& dir_name); | 28 explicit InMemoryDirectoryBackingStore(const std::string& dir_name); |
28 DirOpenResult Load(Directory::MetahandlesMap* handles_map, | 29 DirOpenResult Load(Directory::MetahandlesMap* handles_map, |
29 JournalIndex* delete_journals, | 30 JournalIndex* delete_journals, |
30 MetahandleSet* metahandles_to_purge, | 31 MetahandleSet* metahandles_to_purge, |
31 Directory::KernelLoadInfo* kernel_load_info) override; | 32 Directory::KernelLoadInfo* kernel_load_info) override; |
32 | 33 |
33 private: | 34 private: |
34 DISALLOW_COPY_AND_ASSIGN(InMemoryDirectoryBackingStore); | 35 DISALLOW_COPY_AND_ASSIGN(InMemoryDirectoryBackingStore); |
35 }; | 36 }; |
36 | 37 |
37 } // namespace syncable | 38 } // namespace syncable |
38 } // namespace syncer | 39 } // namespace syncer |
39 | 40 |
40 #endif // SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ | 41 #endif // SYNC_SYNCABLE_IN_MEMORY_DIRECTORY_BACKING_STORE_H_ |
OLD | NEW |