Module holochain::conductor::api

source ·
Expand description

Defines the three Conductor APIs by which other code can communicate with a Conductor:

Each type of API uses a ConductorHandle as its exclusive means of conductor access

Modules§

Structs§

  • Information neeeded to spawn an admin interface
  • Agent info dump with the agent, space, signed time, expires in and urls printed in a pretty way.
  • Info about an installed app, returned as part of AppResponse::AppInfo
  • The concrete implementation of CellConductorApiT, which is used to give Cells an API for calling back to their Conductor.
  • Cloned cell that was created from a provisioned cell at runtime.
  • Storage info for DNA used by one or more hApps.
  • A full view of the DHT shard of the Cell. Ops start in the validation limbo then proceed to the integration limbo then finally are integrated.
  • A high level view of the incoming ops and where they are currently. Ops start in the validation limbo then proceed to the integration limbo then finally are integrated.
  • A collection of many cells dumps for easy viewing. Use display to see a nice printout.
  • The “internal” Conductor API interface, for a Cell to talk to its calling Conductor.
  • A minimal set of functionality needed from the conductor by host functions.
  • State dump of all the peer info
  • Provisioned cell, a cell instantiated from a DNA on app installation.
  • The admin interface that external connections can use to make requests to the conductor The concrete (non-mock) implementation of the AdminInterfaceApi
  • The Conductor lives inside an Arc<RwLock<_>> which is shared with all other Api references
  • Cell whose instantiation has been deferred. Not yet implemented.
  • Response type for storage used by holochain and applications
  • The data provided over an app interface in order to make a zome call

Enums§

Traits§

  • A trait for the interface that a Conductor exposes to the outside world to use for administering the conductor. This trait has one mock implementation and one “real” implementation
  • The interface that a Conductor exposes to the outside world.
  • The “internal” Conductor API interface, for a Cell to talk to its calling Conductor.
  • A minimal set of functionality needed from the conductor by host functions.
  • A trait that unifies both the admin and app interfaces

Type Aliases§