WebAssembly / WebAssembly/WASI
Should wasi-sockets have an opinion about broadcast?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Also, multicast?
I originally raised this question here: https://github.com/bytecodealliance/wasmtime/pull/7148#issuecomment-1747943612
In brief, I'm wondering if it's intended for wasi-sockets to have any special knowledge of UDP broadcast, or if they should be handled implicitly the same way all other restrictions on target addresses are.
If the answer is "it's all just UDP, so we do what UDP does and don't add any weird extras to the API" then would it be worth explicitly drawing attention to this in the spec? E.g. "if in doubt about how this API will behave, assume it is the same as the corresponding behaviour in Berkley sockets" or something?
Thanks! 💖
P.S.: I don't have any strong opinion about this — even about documenting it. I just thought just in case it hadn't been discussed that might be worth raising.
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
Review the linked Wasmtime pull request discussion and the wasi-sockets specification to understand the open question about UDP broadcast and multicast. Done would require an agreed position on whether the API needs special behavior or explicit specification guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100