WebAssembly / WebAssembly/wasi-messaging
Feat: Pending Messages
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 33
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
The protocol need to have some ambient information of the current state of the message stream/buffer.
One of the most useful information to give to a message-handler is the pending-message-count
or at least if a flag for message-pending yes/no/unknown
This will help a consumer to decide when to flush/commit a batch/process,
without it, it is very hard to detect idle periods in a message stream.
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 reading the WASI messaging proposal and its protocol definitions; the issue does not name a file, test, or entry point. Determine whether the protocol should expose a pending-message count or a yes/no/unknown flag, and define how handlers observe it. Done means the proposal specifies the chosen state information and its behavior clearly enough for consumers to use it.
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