opendut
opendut copied to clipboard
eclipse-opendut
Plugin mechanism
We would like to have a plugin mechanism to extend openDuT with functionality for specific use-cases.
We plan to use WebAssembly as portable compilation target for plugins, but there's still various questions about the how.
Goals of the exploration:
- How do we exchange information (data) with plugins?
- Can we allow for everything we need past the sandboxing of WASM (e.g. FS access, root, network-interfaces/CAP_NET_ADMIN)? Are there meaningful usages of the sandboxing?
- How is the usability when developing plugins via Rust?
- Can plugins be developed via e.g. Python? How is usability there?
- Usage of plugins at least in EDGAR Setup.
References:
- Plugins in Rust: The Technologies
- General tutorial
- Transferring complex data types between WASM and Rust
- Interfacing with the OS
- Maybe a solution
- playground with wasmtime experiments
