Expand description
Atomic, file-based HTTP cache.
Lightweight by design: no database engine, no C dependency. Each feed is stored as a
pair of files under the cache dir, keyed by sha256(feed_url):
<hash>.json—CacheMeta(validators + timestamps + content type).<hash>.body— the raw response body bytes.
Both are written atomically (temp file + rename) so a crash can never leave a torn
entry. The cache exists for (a) conditional GET and (b) resolving show / get_item
lookups — it is not responsible for item-ID stability (IDs are deterministic; see
crate::identity).
Structs§
- Cache
- Handle to the on-disk cache directory.
- Cache
Entry - A full cache entry: metadata plus the raw body bytes.
- Cache
List Item - Summary of a cache entry for
rss cache list. - Cache
Meta - Cached HTTP metadata for a feed.