WebAssembly / WebAssembly/WASI
Require network handle
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
wasi-sockets requires a network handle to be passed to operations that talk with the outside world. Example: tcp::connect
/// An opaque resource that represents access to (a subset of) the network.
/// This enables context-based security for networking.
/// There is no need for this to map 1:1 to a physical network interface.
resource network
Even though this network resource is defined in the wasi-sockets repo, there is nothing socket-specific about it.
Should wasi-http require this handle too?
Edit: the http proxy world might do fine without, but I'm mainly coming at this from the cli world perspective.
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 wasi-sockets network resource and the tcp::connect example described here, then compare the wasi-http proxy world with the CLI world. Determine whether HTTP operations should require the handle in each world and document the resulting interface decision in the relevant WASI specification materials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100