Piotr Sikora

I believe most (all?) comments were addressed, but some things might have been lost in the rewrite, so please take a look. Thanks!

@mattklein123 @htuch @yskopets @yuval-k @gbrail @jplevyak @kyessenov could you please review the latest iteration of the ABI spec? Thanks!

Hi @krdln! Could you check the CLA? It looks that the email is on file, but your GitHub username is not.

Thanks, I'm glad that everything works for you! I'll keep the bug open as a reminder to put a list of compatible host environments in the documentation that I'm working...

> How will this work in practice when Envoy WASM picks up the new enumeration from Envoy? Do we expect > > * Envoy-Wasm will pick up the Envoy change...

Hi @casimiro, apologies for the late response, and thanks for the contribution! The current code is fine (otherwise, it wouldn't work with the existing host implementations). The issue is that...

This looks really good, amazing work! Thanks for making it available outside of MOSN - someone asked me about integrating Proxy-Wasm into their in-house Go proxy, and this will be...

Yes, I was a little confused by what exactly did you mean by "contribute" and your question about licensing requirements, thanks for clarifying! Keeping proxy-wasm-go-host within `mosn.io` group sounds perfectly...

The vNEXT is unfortunately still a work-in-progress, and not what Envoy and the existing SDKs are implementing, although I'm actively working on fixing that. Why are you looking at it?...

> How can this be called from Rust? Cannot find a mention of it in the Rust SDK See the answer in [the other issue you've opened](https://github.com/proxy-wasm/proxy-wasm-rust-sdk/issues/97) in the Rust...