Extend Store::Digest to include a way to indicate that an entry ought to be treated as cache.

2024-03-18T18:05:19Z

2025-11-24T22:10:00.000Z

Adding a cache field to Store::Digest will require changing the metadata record, which in turn will create an incompatibility.

Create a variant of the metadata driver for both the old and the new version of the database layout.

Extend Store::Digest to include a way to indicate that an entry ought to be treated as cache.

How do we actually go about evicting expired cache entries?

https://intertwingler.ibis.makethingsmakesense.com/bc4fce9a-fb92-4068-91a4-da9b06996b3d

If an entity is inserted into the store overtop of a cache entry, clear the cache flag and ensure it is never re-enabled.

Implement caching of generated representations against Store::Digest.

Intertwingler MVP

It would be useful to be able to indicate to the engine that a given handler manages a content-addressable store (and thus can be used for caching).

Overhaul Store::Digest.

Reuse the `dtime` field and just set it to the future.

We want Intertwingler to have a unified interface to opaque blob storage, whether a given blob is intended to be persisted or not.

What do we do about the expiration time of the cache entries?

What if a cache entry is superseded by an entity that is durable?