Expand description
§Module Orchestration
Defines the traits and the registry that the kernel uses to manage the lifecycle of native Rust modules and WebAssembly (WASM) plugins.
The micro-kernel does not bake in a single module ABI. Instead it exposes two complementary traits:
Module– implemented by native, in-process Rust modules. Used for the Layer 1 “Native Core” components in the Rust Oxide architecture (network stack, SQLite engine, etc.).WasmModule– implemented by WebAssembly plugins. Used for the Layer 2 sandboxed components (extractors, parsers,oxide-compress, etc.).
The ModuleManager keeps a map of loaded modules keyed by id and drives
them through a small state machine (Loaded -> Starting -> Running -> Stopping -> Stopped).
Structs§
- Module
Manager - Manages the set of modules loaded into the kernel.
- Module
Metadata - Static information about a module supplied at registration time.
Enums§
- Module
Kind - The execution layer / runtime that hosts a given module.
- Module
State - The lifecycle state of a module known to the
ModuleManager.
Traits§
- Module
- Trait implemented by all native, in-process modules.
- Wasm
Module - Trait implemented by WebAssembly plugins.