On Feb 26, 2:16 pm, Alexandre Mah <[email protected]> wrote: > I think you might have misinterpreted the scenario Daniel is > describing. He's not describing the scenario where a client gets > disconnected and then needs to transform operations when it reconnects > (which we can already handle very easily and does not require TP2 at > all). He's describing the case where the server loses its own data > (which is sort of already catastrophic in itself).
But if I'm not mistaken, even the 2nd case still works in the current system. As long the client and server can agree on some past version, the client simply needs to resubmit all deltas starting from that version, and the server can transform and re-apply them. The caveat is that the client will have to store a large number of checkpoint versions, and deltas from each checkpoint to the next. And this is where the commit notice comes in - it tells the client that it can safely discard all deltas up to a certain version, because the server has it stored properly, and can recover on its own up to that point. -- 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.
