Thats the host, but the guess is missing, as stated in the issue last year "I guess we could add sockets to wasip2". To be honest, even BigGo failed me on websocket conns on both wasmtime and wazero (connects and gets into an inf loop on reply). WebWorkers and GOOS=js work like a charm tho on BigGo in FF/chrome.
Comments
For embedded systems, see https://github.com/tinygo-org/net
For WASI, check out WASI Preview 2, https://docs.wasmtime.dev/api/wasmtime_wasi/p2/index.html
Thats the host, but the guess is missing, as stated in the issue last year "I guess we could add sockets to wasip2". To be honest, even BigGo failed me on websocket conns on both wasmtime and wazero (connects and gets into an inf loop on reply). WebWorkers and GOOS=js work like a charm tho on BigGo in FF/chrome.
Yeah, I suspect sockets in wasip2, and wasip2 in general, are just now having the bugs shaken out of them.
The company I work for is just now upgrading its edge WASI support to wasip2.