Comment 5 for bug 778140

Revision history for this message
Seif Lotfy (seif) wrote : Re: Time warp problem in MOVE_EVENT handling

timestamp | uri | current_uri
-----------------------------
00 | A | A
10 | A | A
20 | A | A
30 | B | B
40 | C | C
50 | A | A

move A to T at 35

timestamp | uri | current_uri
-----------------------------
00 | A | T
10 | A | T
20 | A | T
30 | B | B
35* | A | T
40 | C | C
50 | A | A

move T to L at 15

timestamp | uri | current_uri
-----------------------------
00 | A | L
10 | A | L
15* | A | L
20 | A | T
30 | B | B
35* | A | T
40 | C | C
50 | A | A

Problem:
1) we can not trace the origin of 20 since how is the origin uri. A while the current uri is T without having an A -> T or L -> T before 20 occurs
2) the Move event 35* if once is trying to reproduce the event timeline is invalid since A was moved to L already so we need to modify the move event