Hello All, I've been reading the various wave protocol white papers and wanted to understand more about how the OT implementation employed by Wave differs from that described in the Jupiter paper. In particular, the use of server Acknowledgements as noted in the OT white paper:
"Having a simple and efficient server is important in making Wave reliable and scalable. With this goal, Wave OT modifies the basic theory of OT by requiring the client to wait for acknowledgement from the server before sending more operations. When a server acknowledges a client's operation, it means the server has transformed the client's operation, applied it to the server's copy of the Wavelet and broadcasted the transformed operation to all other connected clients. Whilst the client is waiting for the acknowledgement, it caches operations produced locally and sends them in bulk later." I checked out the Fedone code and started digging to try and find where the client caches operation while waiting for an acknowledgement, but the code that does this has not jumped out at me. Looking at ConsoleClient.java, it seems that operations are sent to the server without any handshaking with the server at all. This can be seen when sendAppendMutation() is called in response to user input, which in turn calls backend.sendWaveletDelta(), which invokes submitRequest() on the server. I could not find any code relating to acknowledgements in the server side code either. Is the server acknowledgement and operation caching in the client not implemented in the Fedone example? If it is, can someone please point me in the right direction. Thanks, Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
