On Sun, Jun 20, 2010 at 2:14 PM, John Barstow <[email protected]> wrote:
> On Sat, Jun 19, 2010 at 9:03 AM, Mathijs <[email protected]> wrote: > > Hi all, > > > > For efficient, fully interactive clients, it is beneficial to have > > their (OT) client-path wander off from the server path. > > To do this, it is important that clients are able to recognize the > > deltas they submitted themselves in the constant stream of > > WaveletUpdates. > > > > Currently the FedOne server doesn't support fully interactive clients. > FedOne *does* support fully interactive clients. I implemented one prior to the io2010 release. It is critical that the client know which of the updates corresponds to it's submitted delta in order to perform proper OT. I too had to rely on the current FedOne behavior where the update corresponding to a submit arrives after the submit response. > > > Can anyone confirm that this indeed is part of the specification? > > Or maybe my logic is flawed and there really is no need for this. In > > that case please let me know. > > > > There's really no need for this; as far as the spec is concerned a > fully interactive client should follow the same logic as a federated > server; in other words, never echoing back deltas at all. > The FedOne server has a overly simple model for its clients; you are > much better off looking at the logic used to respond to deltas from > another server. > 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. -Tad -- 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.
