On Mon, Jul 5, 2010 at 1:05 PM, Toshiya Kazuyoshi <[email protected]> wrote: > That is, The data of OT will not be sent to server but accumulated in > a client and that can be saved in a file on a client computer, by > using HTML5 File API. And the file can be loaded back to wave client. >
Well, there are a few things to bear in mind here. I'm dubious about your requirements - you're going to make changes to a wave but not communicate them to anyone? Regardless, you can in fact do this a couple of ways. First of all, you can create a private reply (which has no other participants other than yourself). This is sent to the server, but is never communicated to other servers. So you install your own server, secure it however you like, and federate that to maintain privacy. You don't need a mock server, just a real server with an SSL certificate. This makes implementing the client much simpler and allows for full functionality. Secondly, if the client is capable of OT, you simply never send pending changes to the server. Incoming requests get transformed against pending changes, but you throw away the second half of the transform output instead of sending it to the server. The main issue here is that resync/replay functionality is not going to be particularly easy to implement with a large pool of pending changes to account for. Adding OT to the client is probably less work than actually creating a mock server but more work than installing an actual private server. -- 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.
