On Mon, Jul 12, 2010 at 2:32 PM, Alex North <[email protected]> wrote: > In our experience that is much more work than we envisage rolling out > the OT change to be.
That may be true in your Google-specific deployment, but for those of us with federated servers or alternative implementations there is some non-trivial work that will need to done to production systems. That said, if it fixes the protocol versioning problem then I'm more inclined to consider the proposal. I'm not using the conversation model at all in my code, so I'm a lot more insulated from those design flaws. I'll reserve comment until such time as the protocol versioning proposal has been made. Kudos on doing more design in the open instead of just throwing changes over the garden wall - it certainly feels a much better transition to open development than, say, the Android team have so far managed. -- 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.
