WebAssembly / WebAssembly/WASI
What's in a socket?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Apologies for the uh, vague issue, but not sure of a better way to do this. We want fairly open-ended discussion about what a socket is. A starting point might be to look at how different existing systems handle sockets - say, BSD vs microkernels, and how that affects things like socket options. Or indeed existing sandboxing attempts.
Personally we don't have any resources on hand about this stuff but opening an issue is a good way to get poked about looking into it. :v
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 comparing how existing systems handle sockets, especially BSD and microkernels, and review existing sandboxing attempts. The discussion should establish what a socket means for WASI and how that affects socket options; no specific file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100