itowlson

Well, "just work" might be stretching it. I couldn't get it working with Rust SDK HTTP types, because wasi-hyperium exports its own WASI types and they don't unify. But I...

@lann Let me clarify "the guest" here (because I used it imprecisely earlier). Are you saying: * The guest _Wasm component_ should not see the `wasi:http` interface (there should be...

I pushed a Rust thing at https://github.com/fermyon/wasi-grpc-server-rust. Preliminary for feedback. @fibonacci1729 I considered adding it as a new crate in your existing repo but it looked like I'd need to...

Given the proposal to implement this in guest libraries rather than in Spin, I'm not sure of the best way to track next steps. I've done a Rust library. We...

@seungjin Just to clarify, this issue is specifically about components used in composition rather that directly associated with a trigger - the large manifest problem you mention is maybe more...

I should add that I do like the implications of isolation rather than mere textual splitting. One of the challenges I ran into with the previous attempt at this (which...

+1 for leaving existing interfaces alone. Renaming existing interfaces seems like it would break all existing code. Agree we should make `spin` (or something like that) the namespace for all...

We can create parallel packages and interfaces (e.g. `spin:platform/[email protected]` identical to `fermyon:spin/[email protected]`) as long as we retain the existing packages and interfaces for back compat. Spin must still export the...

The top level package is now `spin:[email protected]`. Existing package names and namespaces are retained for backward compatibility. The following APIs are now accessible via neutral interfaces: * Command trigger: `wasi:cli`...