On Mon, Jun 21, 2010 at 9:42 AM, Tad Glines <[email protected]> wrote: > > No, there really is a need to know which update corresponds to the submit. > Either the specification needs to state that the update (an all subsequent > updates) will be delivered to the client after the submit response, or the > protocol needs to be modified so that the client has a way of correlating an > update to it's submitted delta. This correlation is critical to correct OT > implementation. >
If the client is doing OT according to the spec it will never receive a update corresponding to a submitted delta. The FedOne client does not do OT, which is why there's stuff being echoed back to the client by its server. If both the client and server are tracking client state you run the risk of the states diverging, but I suppose that's the risk on building on top of the FedOne implementation. Mind you I'm doing plenty of things besides tracking Wave development, so I've probably missed an update which completely demolishes my arguments. -- 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.
