Crate holochain_cascade

The Cascade is a multi-tiered accessor for Holochain DHT data.

Note that the docs for this crate are admittedly a bit loose and imprecise, but they are not expected to be incorrect.

It is named “the Cascade” because it performs “cascading” gets across multiple sources. In general (but not in all cases), the flow is something like:

• First attempts to read the local storage
• If that fails, attempt to read data from the network cache
• If that fails, do a network request for the data, caching it if found

Retrieve vs Get

There are two words used in cascade functions: “get”, and “retrieve”. They mean distinct things:

• “get” ignores invalid data, and sometimes takes into account CRUD metadata before returning the data, so for instance, Deletes are allowed to annihilate Creates so that neither is returned. This is a more “refined” form of fetching data.
• “retrieve” only fetches the data if it exists, without regard to validation status. This is a more “raw” form of fetching data.

Modules

• __mock_MockCascade
• __mock_MockCascade_Cascade
• authority
  Functions for the various authorities to handle queries
• error
• test_utils
  Test utils for holochain_cascade

Structs

• CascadeImpl
  The Cascade is a multi-tiered accessor for Holochain DHT data.
• MockCascade
  TODO

Enums

• CascadeSource
  Marks whether data came from a local store or another node on the network

Traits

• Cascade
  TODO