Hi all, In the whitepapers I read about google's "extension" to OT, which mandates that deltas can only ever be submitted against a version on the server's OT path. This means that only one delta can be sent to the server at a time. Remaining client operations need to be buffered, and transformed against incoming updates until the server confirms.
In case the connection is a bit slow, or the server is busy, it's possible that a client has quite a few operations buffered that can be submitted once the server confirms the latest submit. Now the client basically has 2 choices: A) compose all ops in the buffer to 1 op B) just put them all in the delta A. Composing is the easiest/cheapest. Especially since it can be performed while waiting. The only downside is that you will lose some character-by-character typing history (whole words might be submitted as 1 op). B. Since a delta is just a list of operations, the other option is to store all buffered ops there. WaveletDelta's sourcecode mentions the list is orderered, so no risk there. The only downside of this method is that the transformations the client needs to perform are somewhat heavier (since incoming updates need to transform every op in the buffer, instead of just the composed result) So this brings me to my question: Is there any limitation on using B) ? For example a maximum delta size? (number of ops per delta) Or a rule against putting 2 mutatedocument operations for the same Document in 1 delta? Thanks Mathijs -- 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.
