Pat Hickey

Given that the implementation already implies `rustls` for the (overridable) default behavior, I would be in favor of adding a cargo feature for any tls support via `rustls`, and then...

This seems like a good idea to me - thanks @Mossaka. Agreed with Nick.

Hi! Speaking generally for the authors of this spec, we all agree that the two different handler interfaces (and different types for `{incoming,outgoing}-{request,response,body}` generally) is a tremendous amount of unwanted...

Glad this is something you are working on. Exactly how to introduce it is up to you: if you have an interface you are ready to commit to, then putting...

Thanks for working through this, your design looks good to me. I don't have enough expertise in that range of KV stores to be certain all of them support these...

My recommendation for the moment is that you should just use wit-bindgen directly instead of through cargo component. A lot of what cargo component does is just wrap that crate,...

I think moving list-keys to batch seems appropriate unless someone has a reason it isn't. I'd prefer to see the cursor string be replaced with a resource. That means the...

Rust 1.82 includes new wasm features, which I suspect are not yet handled correctly by `walrus` or somewhere else in the `wasm-bindgen` transitive dependencies. For more information: https://blog.rust-lang.org/2024/09/24/webassembly-targets-change-in-default-target-features.html

Argument parsing was hacked in and isnt working particularly well for us, see https://github.com/bytecodealliance/cargo-component/issues/326 . Nobody has had time to address it. You are welcome to send a PR if...

This is a great discussion! Its really cool to see `wit-spell-check`, if that tool had existed prior to stabilizing 0.2.0 we probably would have been nudged to turn `src` and...