WebAssembly / WebAssembly/WASI
[v0.3] Support HTTP Upgrade
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
The HTTP "Upgrade" mechanism allows for a client and server to negotiate switching an HTTP connection to use another protocol. This is most notably used by WebSockets but has a few other uses including the popular WebTransport proposal.
I would expect implementation of this feature to be optional, so it might make sense for it to use separate interface(s) that can take ownership of a request/response and return some stream(-like) resource representing the underlying connection. This could even perhaps live outside of wasi-http itself if we find a good pattern for representing this kind of "interface extension", similar to proposals in WebAssembly/WASI#825.
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 reviewing the HTTP Upgrade mechanism, the WebSockets and WebTransport references in the issue, and the related WebAssembly/WASI#825 discussion. A complete result would define an optional interface extension for transferring request/response ownership and exposing the underlying connection resource.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100