Takeshi Yoneda
Takeshi Yoneda
Hi @hafeidejiangyou, that's a good q! When we first started designing our compiler (which used to be called JIT), I even had no idea whether it was possible to develop...
fyi, the exception support might work with the latest envoy, see the discussion https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/issues/140
I would like to support, but the problem is that semantics of property_get/set are extremely complex... Even I don't get the whole behavior like when the struct is serialized as...
no immediate concern from me! Let's see the concrete necessary API changes and how they can be implemented in our compiler etc. Exciting!
Hi there, the wazero runtime author here. I spent yesterday and actually ported the PoC of @lubinszARM to work with wazero and played around with some gVisor's code base. So...
maybe you want to take a look at #310
as for the list types, I see that Envoy always returns NotFound, which I think is a bug of Envoy.
@zonghaishang the answer here is "it depends on the host implementation". But take Envoy for example, of course, YES and Envoy creates Wasm VMs (each corresponding to plugin) per threads...
> If the contextId is passed to the host, the host will correctly identify the Filter instance and return the HTTP header. And this is unnecessary because Wasm VMs are...