I don't think it's strictly necessary, but it makes merging new edits
simpler and it significantly reduces the chances of collisions between
revision ids, there is less ambiguity. What downsides do your see?
-Damien
On Feb 8, 2009, at 2:28 PM, Adam Kocoloski wrote:
Hi Damien, it seems to me that you're conflating two separate
issues. I agree that the revision history should be trimmed, and
that this will potentially introduce spurious conflicts when two
servers have no shared history for a document. I don't see how this
change by itself requires the addition of a revseq to the JSON
revision format. Is it really required?
Adam
