Visual RFC.
ALL RFCs / RFC 5789
Read the RFC ↗
RFC 5789 / MECHANISM GUIDE

Atomic modification

02

A server must apply the entire set of changes atomically or apply none.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 2 ↗
RFC 5789 · § 2EXAMPLE
3 / 3
Atomic modificationA server must apply the entire set of changes atomically or apply none.Atomic modificationOriginal: A=1Original: B=2Stage: A=3Stage: B=invalidRollback: visible state is still A=1, B=2
03
Keep original state

Neither staged modification becomes the visible final resource.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Do not expose an intermediate partially patched representation.

  • Do not expose an intermediate partially patched representation.
  • If the complete patch cannot be applied, none of its changes are applied.
  • Atomicity covers all directly affected files when the patch format spans them.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Patch versus replacement
  2. Atomic modification
  3. Conditional PATCH
  4. Discover patch formats
  5. Failure and verification

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗