#4215 NORM First D: Unhandled collision scenario while collaborating

[Zarro Boogs per Child]

#4215: Unhandled collision scenario while collaborating
--------------------------------------+-------------------------------------
 Reporter:  uwog                      |       Owner:  uwog                  
     Type:  defect                    |      Status:  new                   
 Priority:  normal                    |   Milestone:  First Deployment, V1.0
Component:  write-activity (abiword)  |     Version:                        
 Keywords:                            |    Verified:  0                     
--------------------------------------+-------------------------------------
 Two testcases lead to unwanted collaboration results:

 1. Make sure to have a big network lag; then within this timeperiod, do
 the following:
 2. Person S shares a document with "123456789" in it
 3. Person C joins the shared document
 4. Person C pastes "foobar" between the '5' and '6'
 5. Person S inserts an 'x' between the '5' and the '6'

 Note that the resulting document looks correct (12345collisionx6789);
 however, the change from person C should have been denied since the
 changes were made in the same document position. In this simple case it
 works OK, but when more complex operations are involved, this will lead to
 unexpected results.

 For example, you can make the documents go out of sync by doing the
 following:

 1. Make sure to have a big network lag; then within this timeperiod, do
 the following:
 2. Person S shares a document with 3x2 table in it
 3. Persion C joins the shared document
 4. Person C appends an 'x' to the document
 5. Person S selects the whole table, and pastes "12345678901234567890"

 The documents are out of sync now, due to the inability to detect the
 collision described above.

-- 
Ticket URL: <https://dev.laptop.org/ticket/4215>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system