Mitosis Usecase Scenarios has been edited by Martin Alderson (Jan 12, 2009).

(View changes)

Content:

This page is intended to identify and discuss all possible usecase scenarios of Mitosis during the refactoring process

  1. When a same entry gets created on more than one master server then only one entry needs to be taken as base and the
    other needs to be removed. But how do we choose which one to retain/discard.?
    • At the moment the one with greater CSN (i.e. the more recent) will be retained just like with any conflicting modification. The older entry is lost - it would be useful if it were moved to a lost+found area and an administrator notified in some way.
  2. When one server deletes an entry while another server adds a child entry below at the same time, what do we do to resolve the conflict?
    • On a single server a delete followed by a child entry add would give an error, as would a child entry add followed by a delete. Perhaps this means we should just discard the second operation?

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences