As, in OT, there is not usually a 'best way' to deal with a conflict, it is
vital for anyone implementing a client (or alternate server that federates)
to know the exact method of conflict resolution used in WiaB for every
possible conflicting case.

Currently, the only way for a developer to learn this is to read the Java
code (which can be quite dense). This has to be done for every developer who
wants to build an alternate client, or compatible server. Not only is this
inefficient, it causes enormous difficulty for people who are not familiar
with Java, and those who just aren't comfortable with porting code between
languages.

As such, I think it is of great importance that someone who has been
involved in building the WiaB (and/or the Google Wave) OT code draw up a
document that details the specific conflict cases, and how they are dealt
with.
--
Nathanael Abbotts

Reply via email to