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§
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
- The built-in implementation of the DPKI service contract, which runs a DNA
- Interface for the AppStore service
- Interface for the DPKI 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
Traits§
- Interface for the AppStore service
- Interface for the DPKI service
- Some more helpful methods built around the methods provided by the service
Functions§
- Create a minimal usable mock of the app store
- Create a minimal usable mock of DPKI
Type Aliases§
- Alias
- Alias