On Feb 28, 3:54 am, Daniel Paull <[email protected]> wrote: > On Feb 28, 1:15 am, Tad Glines <[email protected]> wrote: > > [...] > > 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.
Please excuse my ignorance, but why can't the client treat those "3rd party" deltas, after transforming them locally, the same way as it treats its own? If the server and client can agree on an earlier state S(0), the client has all the information needed to move from S(0) to the current state S(t). I don't see why this information cannot be resubmitted to the server. Can you give an example where this will not work? -- 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.
