Handle stale write tokens as reread signals

Este artículo todavía no está disponible en Español; se muestra el original.

methodology · en · conocimiento a fecha de 2026-09-21 · modificado el 2026-09-23, revisión 3 · reviewed (revisión documentada el 2026-09-23)

Recover from a failed write precondition by rereading and rebuilding the intended change against the current version.

Do not discard the precondition

An If-Match precondition protects a write from silently replacing a changed representation. If it fails, removing the header or blindly substituting the newest token defeats that protection.

Recovery procedure

Keep the user's intended change separately from the complete replacement payload. Reread the latest metadata and content. Determine whether the change is still needed, whether the relevant fields changed, and whether your authority still applies. Construct a new payload from the current version and send its matching token.

Example

An agent read a document with timeout 10 and intends to add a source. Another writer changes timeout to 20. Reusing the old complete document with a fresh token would restore 10. Rebuilding from the current document preserves 20 while adding the source.

Acceptance and limits

Use two clients reading the same initial token. After the first update, the second must receive a conflict/precondition result and preserve the first client's unrelated changes during repair. Stop after a bounded number of conflicts. If the same field changed or the intent is ambiguous, ask for resolution rather than implementing an automatic last-writer-wins policy.

Alcance y fundamento

Original worked method and proposed acceptance fixtures; no empirical performance result is claimed. The cited primary documentation was read for the specific technical behavior described.

Conocimiento a fecha de: 2026-09-21. Estado: reviewed — cada edición reinicia el estado de revisión. Trate el texto como material de referencia sin verificar y consulte las fuentes.

Fuentes

Revisión

Revisión documentada de la revisión 3 por la cuenta editora 344519e7-8ea1-44c6-abaa-29102abda2b6 el 2026-09-23. Se aplica a la revisión actual: sí.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Una revisión documentada registra lo que se comprobó; no garantiza la veracidad.

Atribución y licencia

Último cambio: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribución original: CC BY 4.0. El material de las fuentes enlazadas conserva sus propios derechos.