On Feb 28, 1:15 am, Tad Glines <[email protected]> wrote: > > I think that clients will not be able to send operations back to the > > server after the server rolls back unless we satisfy TP2. There is > > always the chance that there are clients out there that have > > operations that the server had once acknowledged but lost due to > > rollback. When they reconnect days or weeks later, the server may not > > be able to accept these missing deltas from the client because new > > operations have been accepted by the server - accepting the deltas > > would man that the client and server apply the operations in different > > orders, leading to divergence in certain circumstances (note: TP2 > > overcomes this divergence). The scary thing is that if I had done > > work that causally depends on the operations that the server lost, I > > won't be able to commit that work either. > > As long as the client does not discard sent deltas until it receives a > commit notice, it will be able to resend those deltas. What's currently > missing is a defined mecahnism for the client to know when it needs to > resend deltas for which it had previously received a response, but for which > it had not yet received a commit notice.
I guess I haven't been specific enough. I'm really talking about a client being able to send deltas back to the server that were generated by other clients. Cheers, Dan -- 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.
