Implement a bag of chips for sync.

 The bag of chips is a per-client state used by the server. This state is
stored on the client and send back to the server on all communication.

BUG=None
TEST=None


Review URL: https://chromiumcodereview.appspot.com/10916174

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156123 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 9 insertions, 0 deletions

diff --git a/sync/syncable/directory.h b/sync/syncable/directory.h
index b34882f..49d598c 100644
--- a/sync/syncable/directory.h
+++ b/sync/syncable/directory.h
@@ -170,6 +170,10 @@ class Directory {
     int64 next_id;
     // The persisted notification state.
     std::string notification_state;
+    // The serialized bag of chips we were given by the server. Contents are
+    // opaque to the client. This is the serialization of a message of type
+    // ChipBag defined in sync.proto. It can contains NULL characters.
+    std::string bag_of_chips;
   };
 
   // What the Directory needs on initialization to create itself and its Kernel.
@@ -260,6 +264,11 @@ class Directory {
   std::string store_birthday() const;
   void set_store_birthday(const std::string& store_birthday);
 
+  // (Account) Bag of chip is an opaque state used by the server to track the
+  // client.
+  std::string bag_of_chips() const;
+  void set_bag_of_chips(const std::string& bag_of_chips);
+
   std::string GetNotificationState() const;
   void SetNotificationState(const std::string& notification_state);