On Wed 08 Jan 2014 09:37:02 AM EST, Bruno Oliveira wrote:
Is just a suggestion, but if I understood correctly your previous
proposal ‘checksum’ was able to check or validate outdated information. Amirite?!
In my proposal checksum was for the transport. When you send your new
data include the checksum so the server can validate the merge happened
correctly. It wasn't for the storage mechanism.
Or to avoid confusion we can:
1. Get rid of checksum and make use of revisions like CouchDB does.
2. Use the checksum and get rid of revisions
3. Keep both (might exist some overlapping between two concepts)
What do you guys prefer?
--
abstractj
On January 8, 2014 at 12:13:42 PM, Summers Pittman (supittma(a)redhat.com) wrote:
>> And is revision a checksum now?