Hi, I'm implemeting federation with wavesandbox, I create a new wave at wavesandbox, add a user from my own server and and begin to receive ProtocolWaveletDeltas, then, what is hapenning is I'm receiving next duplicated hashed_version.version hashed_version.history_hash
incomingDelta.author "[email protected]" alreadyReceivedDelta.author "[email protected]" incominDelta.history_hash "520E56533F5A8A3EE9068DD1C80D008098F218D5" alreadyReceivedDelta.history_hash "520E56533F5A8A3EE9068DD1C80D008098F218D5" incomingDelta.hashed_version.version 117 alreadyReceivedDelta.hashed_version.version 117 incomingDelta.operation[0].mutate_document.document_id "b+MPDyQ_GhH" (5 operations) alreadyReceivedDelta.operation[0].mutate_document.document_id "b+MPDyQ_GhH" (5 operations) incoming delta and already recived delta shares everything except that operations are completely different, I suppose it is correct, but really I don't understand how hashed_version is generate and how it should be managed on my side to create a consisten document. can please someone point to some source code on FedOne or a document that explain a bit how hashed_version is generated on wavelet host server to depict sequential operations to be applied on document evaluation process? Or just someone that can explain to me a bit how this should be managed? I'm a bit lost on this, should apply first received delta and then next one? should I apply OT to second one against first one, then apply to document as they matchs on hashes_version.version? shouldn't server send to me deltas with a order tag that guarantee order applied on wavelet host server? Sorry me if I'm asking something crazy :) Thank you so much in advance. jesus -- 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.
