Piotr Sikora

@yuval-k you're right, I was under impression that `FilterState` and `DynamicMetadata` were merged together, but it doesn't look that's the case yet (see: https://github.com/envoyproxy/envoy/issues/4929). @Gsantomaggio yeah, it looks like it's...

Most of the SDKs (AssemblyScript, TinyGo, Zig) were contributed by the community. There is nothing stopping someone from implementing C# SDK (and there is nothing in the ABI that would...

> * instantiated multiple filters from the same wasm module > * each running on different listener > * sharing the same vm (I didn't override `vm_id`) I think that's...

> TBH, I wasn't aware of that. I just needed to instantiate the same filter on different listeners, and I've set `root_id` because I felt it made sense 🙃 >...

@krdln I believe the original issue should be fixed via https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/186 and https://github.com/envoyproxy/envoy/pull/17692. If you could upgrade and verify that it doesn't happen anymore, that would be great. Thanks!

Yes, I've been meaning to do this for a while (and I have some examples that are not committed because of that). Please make sure all examples are still built...

> Filter A(context ID:1) and Filter B(context ID:2)are XxxFilter extension instances, Filter A is handling OnHttpRequestHeader，Filter B is handling OnHttpResponseBody, Both Filter instances invoke 'proxy_get_buffer' method to get the HTTP...

> @mathetake thank you for your reply. > It sounds, because envoy is a single-threaded shared WASM VM instance, when the plug-in calls the host, the host can obtain the...

> Currently, each request corresponds to a coroutine(not single-threaded). If the host needs to follow the abi specification and maintain `current context_id` on the host side, we need to lock...

> yes. In order to reduce concurrent locking, multiple WASM VM Instances will also be considered, at least for now, it’s not the best solution. You'll end-up using too much...