|
Description:
|
For more info: http://guide.couchdb.org/draft/consistency.html
a) How to deal with data when client A is online, update the data and the server B? is offline
- Client A will store the updates locally and later when the server comes online send the changes.
- If any other clients have modified the same objects a conflict will occur and one of the clients updates will be denied (unless we have some conflict resolution on the server)
b) How to deal with data when client A is disconnected, update the data and the server B is online
- When client A makes performs an update it will be using an older revision since client B updated in the mean time. This is simliar to step a but reversed.
c) How to deal with data when client A and client B are online. Who has the priority?
- First come first served would be possible. The first to update will generate a new revision. The second to update will be using an old revision, hence a conflict occurs.
- Could clients be weighted perhaps?
d) How to deal with data when client A is online, update the data on the server B and needs to sync with the client C.
- As long as client C has not updated the object is should be possible to notify client C that a new revision is available on the server.
- Another option is that client C discovers this when it tries to sync its updates.
|
