I think the client has to do OT, otherwise how else would it be able to integrate the changes to a modifying string. For another entity to do the OT, the entire string would need to be hosted somewhere and the entire changed string would have to be sent to the client.
But it is interesting to note that if we want to implement a simple client which does not require character level updates, then we can avoid doing the OT on client. On Sep 3, 6:33 am, Soren Lassen <[email protected]> wrote: > I'm not sure what you mean by "they're both doing it". To clarify: > > The wavesandbox browser client does OT. (It runs the same java OT code > as the server, which GWT compiles to javascript on the client.) The > web frontend does not. > > The FedOne client is simpler. It doesn't do OT. > > Soren > > On Thu, Sep 3, 2009 at 1:08 AM, Anthony Baxter<[email protected]> wrote: > > > Actually, yeah, they're both doing it. I misunderstood the original > > question, it wasn't clear. > > > On Wed, Sep 2, 2009 at 10:13, Chris > > Marino<[email protected]> wrote: > >> Hmmmm..... > > >> Actually, I though that the sandbox client *did* do OT, but not the FedOne > >> client. > > >>> The text client was included to show how a client may interact with > >>> the server. The client/server protocol is very simple and for > >>> illustrative purposes only. The client as implemented does not do full > >>> OT - it sends simple updates containing a line of entered text to the > >>> server to apply as a paragraph. There is no reason why the client > >>> could not be extended to use the full OT code, we merely chose to > >>> implement something slightly easier, and also show how one might "talk > >>> wave" without having OT in the client. You will note the interesting > >>> design of the client's inbox - it's sent as a live updating wave. This > >>> is an experiment in the "everything's a wave" paradigm. The > >>> client/server protocol is not intended as a standard at this point. In > >>> the future, we hope to figure out (with help from the community) how > >>> we may get to some standardization. > > >> CM > > >> On Wed, Sep 2, 2009 at 6:40 AM, Anthony Baxter <[email protected]> > >> wrote: > > >>> The web frontend sends the changes to the Google Wave server. It does the > >>> OT. > > >>> On Wed, Sep 2, 2009 at 09:29, sudeep<[email protected]> wrote: > > >>> > Hi; > >>> > When i am on a browser (IE ,Mozilla etc), and i access > >>> > wave.google.com and i login to my sandbox account,i am presented with > >>> > a rich user experience on the browser.Here i am able to edit my data > >>> > real time with other users.The confusion here is in this case where > >>> > does the OT happen,surely it does not happen on the client side (ie.. > >>> > on the browser).So who does the client side transformation ? Is it the > >>> > Wave Front End responsible foe the client side OT ??? Are there any > >>> > documents or presentation which can give me any insight into this. > >>> > Please clarify !!! > > >>> > Thanks & Best Regards; > >>> > Sudeep Kumar > > >>> -- > >>> Anthony Baxter, [email protected] > > > -- > > Anthony Baxter, [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
