As far as I can tell, and if I'm not misunderstanding your question, a local local operation happens immediately, following the intent of having an "Optimistic UI", as Google called it. Only remote operations are transformed and then redrawn.
Could it be that Etherpad has no such distinction? Btw, have you read the Operational Transform (OT) whitepaper? Cheers, PP On 10/05/12 21:21, Dylan Dandelion wrote: > If I understand correctly, the Wave editor handles user events and > processes them to generate operations, which are then applied to the > document result in the visual rendering of the operation. > > This approach is different from Etherpad, which finds DOM nodes that have > changed at regular intervals, and then generates operations, sanitizes the > input and redraws the actual DOM. > > What are some of the advantages and disadvantages of the event-driven > approach versus the diff-ing approach? Why did Wave choose to implement the > editor using the event-driven approach? > -- Paulo Pires
