When a write occurs, it is considered tentative until committed at the primary server. A global ordering is used by the primary server to dictate which of several conflicting writes wins. Once a modification has reached the primary server, it is considered stable . Primary servers have authority, this is a tradeoff which allows data to become stable without hearing responses from all clients and servers. Anti-entropy sessions update these logs accordingly.
Primary servers are responsible for managing revocation lists.
The Rover toolkit attempts to aid the application in adapting to dynamic changes in connectivity, bandwidth, latency, and connection costs. Technology isn't going to make these problems go away, so applications must deal with them. Mobile computers are, and will probably always be, limited and fragile. Since network partitions frequent on wireless links, applications must deal with the issues of availability and consistency. Moreover, application adaptation is very complex.