Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document relationship to WASI #3

Open
dippynark opened this issue Apr 1, 2020 · 2 comments
Open

Document relationship to WASI #3

dippynark opened this issue Apr 1, 2020 · 2 comments

Comments

@dippynark
Copy link

dippynark commented Apr 1, 2020

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).

@mathetake
Copy link
Contributor

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!

@PiotrSikora
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants