Multi-instance: If-Match and conflict mode "fail" across instances #1190

Open
opened 2026-11-21 17:41:23 +00:00 by Cordy · 0 comments
Owner

Follow-up of #742 (batch 10 R6-Q4; batch 11b spec-742b2b non-goals, research-b11-r9 N13). Related but separate: #957 (WebDAV conditional headers on DELETE, MOVE, COPY).

With several instances, an If-Match check and the upload conflict mode fail compare against the file as one member sees it; two members can each pass the check for the same old ETag and both write (last writer wins). Documented in multi-instance.md, Known limitations.

Goal: a cross-member compare-and-write for conditional writes (e.g. a short per-path claim in the coordination store around check plus commit, or a backend conditional write where the backend has one), with tests for two members racing on one ETag, and the Known limitations row removed.

Follow-up of #742 (batch 10 R6-Q4; batch 11b spec-742b2b non-goals, research-b11-r9 N13). Related but separate: #957 (WebDAV conditional headers on DELETE, MOVE, COPY). With several instances, an `If-Match` check and the upload conflict mode `fail` compare against the file as one member sees it; two members can each pass the check for the same old ETag and both write (last writer wins). Documented in multi-instance.md, Known limitations. Goal: a cross-member compare-and-write for conditional writes (e.g. a short per-path claim in the coordination store around check plus commit, or a backend conditional write where the backend has one), with tests for two members racing on one ETag, and the Known limitations row removed.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1190
No description provided.