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.
As far as I can tell, the only way to do this, is by looking at the "version after application" field from the SubmitResponse for that delta. Because of this, it's very important that clients receive their SubmitResponse first, before the WaveletUpdate for that change is received. Therefore, I was hoping this was in the protocol-specification, but I couln't find this. I know the Fedone server implementation currently handles this in the right order, but it would be nice to have this somehow described as mandatory somewhere. 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. Thanks, Mathijs -- 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.
