WebAssembly / WebAssembly/wasi-messaging
Feat: Batch processing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 33
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
It is near always better to process messages from a message bus/stream in small batches.
To add or change the message parameter of the producer and guest func from single to list
would make some sens.
An empty-list could be viewed as flush notification.
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
Start by locating the producer and guest functions and their current message parameters in the WASI messaging proposal. Review how messages move through the message bus or stream, then define the batch and empty-list flush semantics before changing the interface. Done means the batching behavior and API impact are specified and covered by the relevant implementation or proposal tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100