On 29/07/2013 12:21 PM, Andreas Gal wrote:
>
> https://wiki.mozilla.org/User:Gal/SyncDataModel
>
> The title is a bit misleading. The data model is closely tied to the
> protocol and a conflict avoidance mechanism (push notifications), which
> are discussed as well.
>
> Please poke holes in this.
More a question than a hole, but: What value is CouchDB providing in
this scheme?
Maybe I'm missing something, but ISTM that the proposed data
representations could all be implemented on top of the existing sync1.1
protocol, with very similar effect.
Two possible bits of value-add that I can see:
* CouchDB might make some races or edge-cases a little cleaner, since
it's version-driven rather than timestamp-driven
* "Future iterations might do merging at read time in presence of
_conflicts" is indeed a nice future possibility
Do you have other benefits in mind as well?
Some other miscellaneous comments:
> jsondiff
As Nick mentioned, encryption could easily defeat this in practice.
We could encrypt just the payloads while exposing the structure of the
document, but I don't recall any discussion of whether that's acceptable
from a privacy POV.
> We should use SPDY to enable content compression.
Again, encryption could defeat the benefits of this in practice.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
