WebAssembly / WebAssembly/WASI
Should `outgoing-handler::handle` consume its parameter?
Open
Nobody has claimed this yet.
P-http
S-inactive
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Should outgoing-handler::handle consume its outgoing-request parameter such that it can't be sent again, or should it be possible for an application to create a single request and send it multiple times?
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 with the outgoing-handler::handle API and its outgoing-request parameter, then review the surrounding WASI HTTP semantics to compare consuming a request with allowing reuse. Done means the ownership behavior is decided and the resulting contract is documented, with any affected specification or tests identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100