gwsystems / gwsystems/sledge-serverless-framework
WASI Reactor Pattern
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 124
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we only support WASI modules with a main that expose wasmf__start. However, WASI also has a "reactor pattern," whereby a module might export multiple functions and the runtime has to call wasmf__init manually. This potentially allows for a nanoprocess to be retained in memory, "kept warm," and used for several function invocations.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how WASI modules exposing wasmf__start are loaded and invoked, then determine where wasmf__init and exported functions would be handled. Done means supporting reactor modules that initialize manually, expose multiple callable functions, and keep a nanoprocess warm across invocations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100