Inter-applet communication
Open
crate:api
crate:scheduler
for:usability
needs:design
- Dominant language
- Rust
- Stars
- 188
- Forks
- 41
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 12
Description
Design questions:
- We probably don't want to use WebAssembly linking, because we want each applet to have its own store (see #48). This means that data would need to be copied since one applet cannot access the memory of another applet.
- The applet could use the import and export functions mechanism. There would need to be a naming convention probably, like `ipc_` prefix. Another option would be a generic IPC syscall.
- How to deal with sending buffers? Probably another IPC to write or read a buffer to an index (shared with the other applet). The [memory-control](https://github.com/WebAssembly/memory-control) WebAssembly proposal seems to be a solution.
Contributor guide
Assessment
This issue has not been assessed yet.