On Thu, Jun 25, 2009 at 05:37:21PM -0400, Damien Katz wrote: > Integrity will be preserved by use of Content-MD5
Bike shed: what about the stronger SHA family of hashes? > But it still is specific to the version of CouchDB and it's dependencies > (version of Erlang, version of ICU, etc). It usually be the same across > versions, but is not guaranteed. If we're doing content hashing, why would this matter? > Optionally will allow that if 2 clients make byte identical saves for a > document, they will get the same revision, and you don't need to return a > conflict error the second client to save. Are there any security issues around possible hash collisions? > I think this is the most pragmatic way to do deterministic revs and integrity > checking. That is, do as little as possible and let others deal with the > problems and implications of canonicalization if they want to to do end to end > integrity checking. Seems like a reasonable approach to me. Best, -- Noah Slater, http://tumbolia.org/nslater
