Skip to content

RFC: should the content API support a write precondition? #161

Description

@HMarzban

Problem

PATCH /api/documents/:documentId/content has no precondition header. Two callers that read the same document and then write both succeed, and the second silently discards the first.

What to decide

Whether to add If-Match, carrying either a document checksum or a revision number. This was deliberately cut once.

Acceptance

  • A yes or no is recorded in this issue.

Notes

Node targeting reduces how often a caller needs this, so consider it after that decision rather than before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions