On Fri, Jul 26, 2013 at 8:58 PM, Andreas Gal <[email protected]> wrote: > The CouchDB protocol has some properties where I am not convinced that its a > good fit for us. Amongst others, each document has an unlimited history that > is tracked locally. This is actually needed for multi-party replication. I > would like to understand how we will deal with this. Lets say we use a > shadow copy in couchdb. What do we do with history? This question is > particularly important to get right, because technically speaking for a sync > scenario where you have 1 server that replications with many clients, but > each of those clients only replicates with that 1 server, we don't really > have to maintain any history in the clients to be able to replicate, if I > understand the couchdb replication protocol correctly. With pure pouchdb we > would be storing that history for no reason, using up disk space beyond the > mere lets-store-everything-twice property of a shadow copy.
Yes, I think the revision history is only used to help conflict resolution, that is, to track ancestry of document revisions. If that's not needed, you can dump the history (Apache CouchDB actually supports this through a _purge API call). Cheers, Dirkjan _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
