On Sep 9, 9:33 pm, Michael K <[email protected]> wrote:
> Without reading the necessary material, my guess is that
>
> deleteCharacters("def")
> characters("def")
>
> can be concatenated to
>
> retain(3)
I'm aware that certain OT frameworks can perform this normalization
without breaking the underlying OT algorithm. But empirically, Google
Wave does not perform this normalization. And I _think_ there are good
reasons for this, at least once the first deleteCharacters("def") has
been propagated. As far as I can tell, an implementation which
performs this normalization will corrupt waves. (Of course, it's safe
to perform this normalization when no other participant in the
protocol can see either of the operations involved.)
AFAICT, the OT algorithms which allow arbitrary cancellation of an
operation and inverse are all more complicated that Wave. In other
words, I believe this is a deliberate design decision, and not a
shortcoming in the operation composer.
Cheers,
Eric
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---
