Module holochain_types::dht_op

Data structures representing the operations that can be performed within a Holochain DHT.

See the item-level documentation for DhtOp for more details.

Modules

• error
• facts
  Facts about DhtOps

Structs

• OpOrder
  This is used as an index for ordering ops in our database. It gives the most likely ordering where dependencies will come first.
• RenderedOp
  The data rendered from a wire op to place in the database.
• RenderedOps
  The full data for insertion into the database. The reason we don’t use DhtOp is because we don’t want to clone the entry for every action.

Enums

• DhtOp
  A unit of DHT gossip. Used to notify an authority of new (meta)data to hold as well as changes to the status of already held data.
• DhtOpLight
  A type for storing in databases that don’t need the actual data. Everything is a hash of the type except the signatures.
• DhtOpType
  This enum is used to
• OpNumericalOrder
  Type for deriving ordering of DhtOps Don’t change the order of this enum unless you mean to change the order we process ops
• UniqueForm
• WireOps
  Condensed version of ops for sending across the wire.

Functions

• action_to_op_types
  Produce op types from a given Action.
• produce_op_lights_from_iter
  Produce op lights from iter of (action hash, action, maybe entry).
• produce_op_lights_from_record_group
  Produce all the op lights from this record group with a shared entry
• produce_op_lights_from_records
  Produce all the op lights for tese records
• produce_ops_from_record
  Produce all DhtOps for a Record

Type Definitions

• DhtOpHashed
  A DhtOp paired with its DhtOpHash