There's been some discussion about wave and how things would be much better if wave supported TP2.
Currently all deltas must be sent to the wavelet host, or owner, for transformation before the delta can be propagated to all other wavelet readers. This means that Wave doesn't support the OT property TP2. If wave supported TP2, then there would be no need for a wavelet "owner" and each server could arrive at the consistent wavelet state independent of each other. Put another way: without TP2, the wavelet "owner" is the single point of failure. With TP2, there is no single point of failure, and no "owner". And there's the problem, no owner means no control. In order for wave to be successful there needs to be a wavelet "owner". The "owner" can enforce schemas and enforce access control policies. If wave supported TP2, then it would be impossible for a server to prevent a another server from writing to the wavelet. One could expect all the servers to "play nice together" but there is no way to explicitly enforce access control policies in a TP2 environment when the servers are owned and operated by separate entities. -Tad -- 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.
