2 ms·
WASI Preview 1 and WASI Preview 2 can do file and network I/O IIUC. Re: tty support in container2wasm and fixed 80x25 due to lack of SIGWINCH support in WASI P
by westurner 2y ago
WASI Preview 1 and WASI Preview 2 can do file and network I/O IIUC.
Re: tty support in container2wasm and fixed 80x25 due to lack of SIGWINCH support in WASI Preview 1:
https://github.com/ktock/container2wasm/issues/146 https://github.com/ktock/container2wasm/issues/146
The File System Access API requires granting each app access to each folder.
jupyterlab-filesystem-access only works with Chromium based browsers, because FF doesn't support the File System Access API:
https://github.com/jupyterlab-contrib/jupyterlab-filesystem-access https://github.com/jupyterlab-contrib/jupyterlab-filesystem-...
The File System Access API is useful for opening a local .ipynb and .csv with JupyterLite, which builds CPython for WASM as Pyodide.
There is a "Direct Sockets API in Chrome 131" but not in FF; so WebRTC and WebSocket relaying is unnecessary for WASM apps like WebVM:
https://news.ycombinator.com/item?id=42029188 https://news.ycombinator.com/item?id=42029188
- westurner 2y agoWASI Preview 2: https://github.com/WebAssembly/WASI/blob/main/wasip2/README.md https://github.com/WebAssembly/WASI/blob/main/wasip2/README.... : > wasi-io, wasi-clocks, wasi-random, wasi-filesystem, wasi-sockets, wasi-cli, wasi-http