385
edits
Services/Sync/Developer/StorageFormat: Difference between revisions
Jump to navigation
Jump to search
Services/Sync/Developer/StorageFormat (view source)
Revision as of 15:22, 30 March 2010
, 30 March 2010→Changes from v1 -> v2: meta/global
(→Changes from v1 -> v2: cryptowrapper) |
(→Changes from v1 -> v2: meta/global) |
||
| Line 38: | Line 38: | ||
== Changes from v1 -> v2 == | == Changes from v1 -> v2 == | ||
The <tt>storageVersion</tt> is now an integer (2) instead of a string, e.g., "1.1", and will only change when the storage format changes. It will no longer automatically changed to the newest client to write the record and instead only change on an incompatible storage format change. | |||
There is an <tt>engine</tt> object that has engine names as its fields with corresponding value objects with two fields: <tt>syncID</tt> and <tt>version</tt>. The <tt>syncID</tt> for an engine changes when the data for that engine drastically changes, and the client will respond by re-syncing all of its data. The <tt>version</tt> of an engine acts like the <tt>storageVersion</tt> and indicates the Browser Object version for the corresponding data. | |||
== Version 1 == | == Version 1 == | ||