Expand description
Central SQLite state store (PRD §10, §11).
One database for every download, in the platform’s data directory — not a
sidecar .part.json next to each file. That is what makes rget list,
rget resume --all and cross-run recovery possible.
Durability rules live in docs/CRASH_CONSISTENCY.md. The one that matters
here: Store::commit_progress is the only way range progress becomes
persistent, it is a single transaction, and the engine calls it only after
an fdatasync of the destination file.
Structs§
- Download
Record - Progress
Update - One durable progress update, produced by the committer after its barrier.
- Range
Record - Store
Enums§
Constants§
- OPEN_
END - Sentinel
endfor a range whose length is unknown (noContent-Length). Round-trips through SQLite’s i64 columns unlikeu64::MAX.
Functions§
- mint_
cookie - A random 128-bit token, used as the destination file’s identity cookie.
- now