You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
What happens when two people edit at once?
A shared address does not decide how stale edits are handled.
Alice and Bob both read the report title “Draft.” Alice changes it to “For review.” Bob still has the old page and then submits “Meeting version.” If the system simply accepts the later write, Alice’s change may be overwritten.
One approach is a version-conditional write. Bob submits the change together with “I edited version v1.” A supporting implementation checks the current version. If it has become v2, it rejects the stale write so Bob can obtain the new content and decide what to do.
The labels v1 and v2 are illustrative. Real version values can use different formats. Consumers should preserve and return them unchanged, without parsing them or comparing versions across Providers.
AFS write options can express an ifMatch condition. Confirm that the Provider declares and enforces the corresponding capability before relying on it. A common interface does not automatically give every resource identical concurrency guarantees.
On conflict, an interface can keep Bob’s unsaved text and show the latest content so a person can merge or rewrite it. Blindly repeating the stale write is not conflict resolution. Automatic merging depends on the content and application rules.
Go deeper
Check your understanding
Why not repeatedly submit the same edit after detecting a stale version?
The content may have changed. Read the current version and decide how to merge or rewrite under application rules.