WebAssembly / WebAssembly/WASI
outgoing-body flush behaviour states
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
As far as I can tell, outgoing-body's stream can exist in two different states:
- unattached to the http request, before the request is made - all writes buffer, and flush is effectively a no-op.
- attached to the outgoing http request after it has been made - in this state, flush functions correctly.
In state (1), does the subscribe just fail if we exceed the high watermark? Or is the high watermark functionality also disabled?
Effectively, does that mean that a transition from state (1) to state (2) change it from permitting writes over the high watermark to not?
Contributor guide
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 outgoing-body stream behavior described in the issue, focusing on the transition between unattached and attached states and the high-watermark question. Document whether writes and flush behave differently across that transition, so the final guidance answers both questions explicitly.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100