Confirmed users
471
edits
(more current-design details) |
|||
| Line 42: | Line 42: | ||
== Synchronization == | == Synchronization == | ||
We've developed the [[Identity/CryptoIdeas/04-Delta-Sync|Delta-Sync]] protocol for getting full sets of encrypted key-value records from browser to server and back again. | |||
However we are currently (04-Jun-2013) investigating a scheme named "Queue-Sync" for uploading batched change records to the server and merging downstream records back into the local datastore. When compared to Delta-Sync, we expect Queue-Sync to: | |||
* avoid expensive full-dataset hashes to compute revision identifiers (but also gives up on some full-dataset integrity guarantees) | |||
* handle "re-sync" more naturally (which occurs at initial connection, and later when either server or browser falls behind) | |||
* avoid keeping a full shadow copy on the browser | |||
== Storage Server Authorization == | == Storage Server Authorization == | ||