Bailey Hayes

You're essentially looking at a piece of middleware. It doesn't define the upstream API and this is an adapter for things like serialization. The other smithy files in the repo...

This appears to have been completed with the latest changes having landed with https://github.com/bytecodealliance/wasmtime/pull/6791

Implementing a capability-provider that implements `wasi-messaging` would be easy-peasy, but I don't think that's what you're looking for. Another useful capability provider that I also don't think you're looking for...

I wonder how "out there" of an option would it be to upstream into NATS for a libp2p mode? Seems daunting but this would also be a value add for...

Thank you for the report! The template does need to be updated. The workaround is to align dependencies manually. We are actively working on a new provider SDK that is...

I'd like to see this. I've switched off `choco` to exclusively use `winget` when developing on windows.

Some of the questions I have so far: - [ ] Which rust library should we provide for initial tier 1 support in wasmCloud? Preference towards `sqlx` as I have...

The key reason why I want a representation for a connection/session is so that we have the ability to run optimizations like creating a connection pool as part of the...

This appears to be a decent choice: https://crates.io/crates/figment

I am separating my responses into multiple comments to make it easier to respond to individual ideas. > Support both WASIp1 and WASIp2 in WASI-libc and other tools Maintainers (including...