Hi Dan, > > So if the delta has been submitted to the server successfully, then your > > client should receive an acknowledgement > > "Should" is the prominent word in that sentence. As it stands, the > client/server interaction between the FedOne client and server does > not even remotely resemble the OT whitepaper published by Google. Of > note here is the lack of server acknowledgements.
What I meant was TCP acknowledgement. Of course for whatever reason the server can behave strangely and does not update the delta change to the document. But I would have thought that the server WILL apply the change unless it crashes or something. Thus the latest delta change would not have taken effect, and the client will need to track back to its previous version of the document. I think the problem lies in the FedOne console client not having OT implemented. This means that the client will be unable to track back to its previous version of the document, I think. As it is, with regards to the FedOne console client, it will retrieve the whole document or the full history (less the latest change) from the server (and I mean the sandbox server here, not the FedOne server). I agree with you that the FedOne console client is not a reference implementation for wave client, and there are still much to do between client and server... cheers, Chiang
-- 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.
