- changed status to open
Implement Vector Clock for Sync
Issue #2619
open
Currently the sync uses the timestamps of the post for detecting conflicts. This has the downside, that the time of the syncing systems must be in sync, too. Vector clocks can generate a partial ordering of events without using timestamps.
Please implement a vector clock.
Steps:
- create a sync_clock table: username, intrahash, system_uri, counter
- add a plugin that increases the clock vector for the updated resource by one. (attention also tag updates and other batch updates must increment the clock)
- Implement the vector clock as output of the sync plan (xml, …)
- Implement a mechanism to update the vector clocks of other systems / adapt the sync conflict detection to use the new vector clocks
Comments (1)
-
reporter - Log in to comment