WebAssembly / WebAssembly/WASI
Clarifying abort behaviours
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
It could be worth further clarifying the drop & abort behaviours at various stages of the lifecycle of a request and response concretely, since these are observable implementation details in HTTP.
Specifically -
- Should the destructor for a FutureIncomingResponse that has not resolved abort the request?
- A drop of a FutureIncomingResponse should probably also therefore also invalidate the outgoing body, so that any writes or finish calls shouldn't work.
- Should dropping an incoming-response or incoming-body or input-stream for a response also cause the connection to be immediately aborted?
And similarly for the server handler cases as well.
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
No files or tests are named. Start by reviewing the request and response lifecycle cases described here, including FutureIncomingResponse, incoming bodies, input streams, and server handlers; done means reaching concrete decisions for each drop, abort, invalidation, and finish behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100