CultLib/src/GameCult.Caching/Contracts
Repository files (latest commit first)
Filename Latest commit message Latest commit date
x 574dba0a64 CultNet publishes every committed cache change once
CultNetDatabase watched OnUpdate, which fires for loads alone, so cache.Commit,
cache.UpsertAsync, variant dependents re-resolved by a base edit and Flatten never
reached subscribers or the mutation log, and a load removal carried an empty key.
The database now observes cache.Watch, the one owner of admitted changes. A write
door of the database (PutAsync, DeleteAsync, ApplyPut/Delete, replica apply, sync)
marks the key it is committing and publishes that change itself, since it carries
the shard-log entry; every other change publishes from the cache, keyed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-29 12:21:14 +02:00
..
cultcache-persistence-format.md C# core: variant records, top-level Set overrides, resolution in the admitting hold 2026-09-29 03:51:53 +02:00
cultcache-schema-compatibility.md Variant overrides follow the plain-record outcome; bad writes and shared indexes are refused 2026-09-29 06:58:51 +02:00
cultcache-store-composition.md CultNet publishes every committed cache change once 2026-09-29 12:21:14 +02:00