Soni L.

we think wasi should implement full posix signal handling. the most obvious benefit is that wasi can show everyone else how to make it safe. in fact... wasi already has...

we understand. in POSIX, signal handlers are mostly used to hardware-accelerate null checks (in e.g. the JVM; this can't be replaced with signalfd), but wasm traps work slightly different from...

sometimes you really want both file and dir contents in the same filesystem node. some systems use these for resource forks. since POSIX doesn't have file-dir duality, and arguably forbids...

how much should it cost to translate between wasi-sockets and BSD sockets? (ideally, the equivalent of a table lookup?)

alright. do you think a compositional socket model would be appropriate for wasi? you ever think about how TCP and UDP are the only transport protocols and get upset that...

ah yeah. we mean, in a real microkernel you'd have a single tcp daemon, so dualstack sockets would still work fine there. but yeah.

not particularly. we still think it's important to look back on existing implementations and understand their pain points and where they break down, but yeah we think that's about all...

to put it simple an embedder would have to provide NAT64 (unwrapping IPv6 packets into IPv4 packets) and DNS64 (converting IPv4 DNS records into IPv6 DNS records) which are fairly...

On the other hand using a string (or something like it) means POSIX could add support for it. Being able to expose application structure to OS firewall would be amazing,...

The usual way to do it in POSIX (or really anywhere, at least today) is to nag a project's developers to add individual SOCKS proxy settings for the app's different...