Skip to content

Document SyncBackend applyOps visibility contract#139

Draft
marcus-pousette wants to merge 2 commits into
cybersemics:mainfrom
marcus-pousette:docs/sync-backend-applyops-contract
Draft

Document SyncBackend applyOps visibility contract#139
marcus-pousette wants to merge 2 commits into
cybersemics:mainfrom
marcus-pousette:docs/sync-backend-applyops-contract

Conversation

@marcus-pousette
Copy link
Copy Markdown
Collaborator

Summary

  • Documents SyncBackend.applyOps as a read-after-write boundary.
  • Adds an explicit backend contract assertion that applyOps results are visible through listOpRefs, getOpsByOpRefs, and maxLamport after resolve.
  • Removes a stale conformance polling path that implied async backends could resolve sync before applyOps was visible.
  • Clarifies that FlushableSyncBackend is only a test/benchmark utility, not part of the normative sync backend contract.

Fixes #112.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document SyncBackend applyOps as read-after-write visible

1 participant