Connor Smith

Thanks for the clarification on security. I was thinking about complexity/further coupling of the provider instance to the host, but I see that's by design, and it makes sense 👍...

@thomastaylor312 should we move this to the wasmCloud repo?

I think @brooksmtownsend has been doing this with the new examples so far: - https://github.com/wasmCloud/wasmCloud/tree/main/examples/rust/actors/http-hello-world - https://github.com/wasmCloud/wasmCloud/tree/main/examples/golang/actors/http-hello-world @thomastaylor312 is there more you'd like to see here? Should we actually create...

Another option, since `is_wasm` is pretty low-level and takes a byte array, is to refactor `get_caps` and `handle_provider_archive` to be consumable by other clients. Something like `inspect(path)` which can handle...

Note that `is_wasm` has been refactored away, but `get_caps` is there, so there's still opportunity to expose this for other clients

Depending on how costly it is, this would be a great thing to run regularly against the host, so we can track performance improvements/regressions 👍

@thomastaylor312 what would you like to do with this issue? Should I pin it?

@thomastaylor312 was this okay to close as stale?

> I'm not sure this argument applies here - as it stands, wasmCloud is already a dependency of wash - `wash up` does not work without wasmCloud being available Starting...