Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 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 | |
| 3 // found in the LICENSE file. | |
| 4 | |
| 5 #ifndef SYNC_SYNCABLE_NIGORI_HANDLER_H_ | |
| 6 #define SYNC_SYNCABLE_NIGORI_HANDLER_H_ | |
| 7 | |
| 8 #include "sync/internal_api/public/base/model_type.h" | |
| 9 | |
| 10 namespace sync_pb { | |
| 11 class NigoriSpecifics; | |
| 12 } | |
| 13 | |
| 14 namespace syncer { | |
| 15 namespace syncable { | |
| 16 | |
| 17 // Sync internal interface for dealing with nigori node and querying | |
| 18 // the current set of encrypted types. Not thread safe, so a sync transaction | |
| 19 // must be held by a caller whenever invoking methods. | |
|
tim (not reviewing)
2012/08/14 02:32:20
Convention would be to have a transaction pointer
Nicolas Zea
2012/08/14 23:24:51
Done.
| |
| 20 class NigoriHandler { | |
| 21 public: | |
| 22 NigoriHandler(); | |
| 23 virtual ~NigoriHandler(); | |
| 24 | |
| 25 // Apply a nigori node update, updating the internal encryption state | |
| 26 // accordingly. | |
| 27 virtual void UpdateFromNigori(const sync_pb::NigoriSpecifics& nigori) = 0; | |
|
tim (not reviewing)
2012/08/14 02:32:20
I think ApplyNigoriUpdate is a better name here...
Nicolas Zea
2012/08/14 23:24:51
Done for first part. What do you mean by change th
| |
| 28 | |
| 29 // Store the current encrypt everything/encrypted types state into |nigori|. | |
| 30 virtual void UpdateNigoriFromEncryptedTypes( | |
| 31 sync_pb::NigoriSpecifics* nigori) const = 0; | |
| 32 | |
| 33 // Returns the set of currently encrypted types. | |
| 34 virtual ModelTypeSet GetEncryptedTypes() const = 0; | |
| 35 }; | |
| 36 | |
| 37 } // namespace syncable | |
| 38 } // namespace syncer | |
| 39 | |
| 40 #endif // SYNC_SYNCABLE_NIGORI_HANDLER_H_ | |
| OLD | NEW |