You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proxy-Wasm is irrelevant to WASI (at least as of preview1), and this spec repository is only about these Proxy specific functions, etc. How WASI will be exposed to the Wasm binary is implementor-speicifc, so I will close this issue. Thanks!
Proxy-Wasm is irrelevant to WASI (at least as of preview1), and this spec repository is only about these Proxy specific functions, etc. How WASI will be exposed to the Wasm binary is implementor-speicifc, so I will close this issue. Thanks!
This is not true, and we rely on select WASI hostcalls in Proxy-Wasm and the relationship with WASI and future plans regarding it should be documented.
This may be somewhere already that I can't find, but I think it'd be useful to document the relationship of proxy-wasm to WASI as it feels like they have the same goal just in different host environments: https://stackoverflow.com/questions/60969344/what-is-the-relationship-between-wasi-and-proxy-wasm
Are the ABI specs completely different or is there some interoperability (potentially in the future).
The text was updated successfully, but these errors were encountered: