3.2.2.4 Conflict Resolution: Exchange in Multiple Sessions with Persistent Data Store

Figure 3.2.2.4-1 shows an example workflow for resolving data conflicts resulting from updates and exchange during multiple sessions with persistent data store.

Figure 3.2.2.4-1 Conflict resolution: exchange with alternative persistence.

The scenario is similar to the single-session scenario:

1. Software A exports EPC_A.
2. Software A saves (persists) H and F in alternative storage (for example, a database), then Software A Session1 is closed.
3. Software B imports EPC_A and edits are made to H, creating H*.
4. Software B exports document EPC_B: H* and F (no changes).
5. Software A begins a new session, Session 2, and reloads H and F from alternative storage.
6. When Software A imports EPC_B into Session 2, Session2 has enough information to know without using EPC_A that:

• F has not been modified, and does not have to be reloaded.
• H* is an edited version of H; there is enough information to let a user decide how to reconcile the two versions.