Expand description
Habery: single owner of the keystore, database and event processors shared by
all local identifiers (Habs), the Rust counterpart of keripy’s Habery.
Memory model: a Habery owns exactly one Manager (and its Keeper), one
Baser, one Kevery, one Revery and one handler-less Parser. A Hab
is a short-lived view that borrows those components, so every Hab sees the
same key state and the same set of local prefixes. Nothing here locks,
spawns threads, or is async: callers decide where a Habery lives (on the
stack in a CLI, on an owner thread in a server, behind their own Mutex).
On open, state is rebuilt from the database (local Habs, local prefixes,
and key state for every known AID), so short-lived and long-lived users run
the same code.
Structs§
- Group
Members - Membership of a local group (multisig) Hab (keripy
GroupHabmhab/smids/rmids). - Habery
- Habery
Options - Options for
Habery::open. - Make
HabArgs - Inception parameters for
Habery::make_hab. All fields default to the same values asHab::make(and keripy’smakeHab).
Functions§
- route_
message - Route one parsed message to the processor that handles it. Shared by
Habery::ingestandBaseHab::ingest_localso there is one dispatch path.