Expand description
Conductor Services
The conductor expects to be able to interface with some arbitrarily defined “services” whose implementation details we don’t know or care about. We want well-defined interfaces for these services such that a third party could write their own.
Modules§
- The Holochain Development Kit (HDK) provides high and low level functions for writing Holochain applications.
Structs§
- The built-in implementation of the app store service, which runs a DNA
- Initialized for ConductorService: just the CellIds that are used for each service
- The set of all Conductor Services available to the conductor
- Data needed to initialize the Deepkey service, if installed. FIXME: this assumes that DPKI will be implemented by a cell, which may not be the case in general. To generalize is currently out of scope.
- A deterministic entry that contains only the cord 32 bytes of a key
- Interface for the AppStore service
Enums§
- This doesn’t exist yet. We need to define it.
- The errors which can be produced by the AppStoreService
- The errors which can be produced by DPKI
- Registration information used to validate operations on a
KeyAnchor
Constants§
- This magic string, when used as the installed app id, denotes that the app is not actually an app, but the DPKI service! This is now a reserved app id, and is used to distinguish the DPKI service from other apps.
Traits§
- Interface for the AppStore service
Functions§
- Create a minimal usable mock of the app store
Type Aliases§
- Alias
- Alias