update example configs and READMEs (#47)

Signed-off-by: markfisher <mark@modulewise.com>

Author: markfisher

README.md

@@ -23,18 +23,18 @@ config.locale = "fr-FR"
 
 [component.translator]
 uri = "./lib/translator.wasm"
-imports = ["http", "io"]
+imports = ["http"]
 
 [capability.http]
-uri = "wasmtime:http"
-
-[capability.io]
-uri = "wasmtime:io"
+type = "wasi:http"
 ```
 
 </td>
 </tr></table>
 
+> [!NOTE]
+> This project is still in an early design phase. All configurations and implementations are subject to change.
+
 ## Core Concepts
 
 The best way to learn the core concepts of Composable Runtime is to go through the step-by-step overview in the [Sailing the 7 Cs with Composable Runtime](examples/7cs/README.md) example.

examples/7cs/README.md

@@ -124,7 +124,7 @@ $ ./run.sh 3
 </td>
 <td>
 
-Host capabilities provide the interfaces a component needs to interact with the external world. For example, the `wasmtime:http` capability enables a component to make outgoing HTTP requests.
+Host capabilities provide the interfaces a component needs to interact with the external world. For example, the `wasi:http` capability enables a component to make outgoing HTTP requests.
 
 The translator is now replaced with one that calls an external HTTP API. The `translate-api.js` implementation is slightly less simplistic as it also knows how to translate "World" into the same handful of languages.
 
@@ -142,7 +142,7 @@ uri = "./lib/capable-translator.wasm"
 imports = ["http-client"]
 
 [capability.http-client]
-uri = "wasmtime:http"
+type = "wasi:http"
 ```
 
 ```
@@ -185,7 +185,7 @@ uri = "./lib/logging-advice.wasm"
 imports = ["logging-stdout"]
 
 [capability.http-client]
-uri = "wasmtime:http"
+type = "wasi:http"
 ```
 
 ```
@@ -240,7 +240,7 @@ uri = "./lib/logging-advice.wasm"
 imports = ["logging-stdout"]
 
 [capability.http-client]
-uri = "wasmtime:http"
+type = "wasi:http"
 ```
 
 ```
@@ -304,7 +304,7 @@ path = "/hello"
 channel = "names"
 
 [capability.http-client]
-uri = "wasmtime:http"
+type = "wasi:http"
 ```
 **ops.toml**:
 
@@ -319,11 +319,7 @@ And finally, the shared `infra.toml` used for examples 4-7:
 ```toml
 [component.logging-stdout]
 uri = "./lib/wasi-logging-to-stdout.wasm"
-imports = ["stdout", "wasip2"]
-
-[capability.stdout]
-type = "wasi:cli"
-inherit-stdout = true
+imports = ["wasip2"]
 
 [capability.wasip2]
 type = "wasi:p2"

examples/7cs/configs/infra.toml

@@ -2,11 +2,7 @@
 uri = "./lib/wasi-logging-to-stdout.wasm"
 # could provide this here instead of the wkg pull in build.sh:
 # uri = "oci://ghcr.io/componentized/logging/to-stdout:v0.2.1"
-imports = ["stdout", "wasip2"]
-
-[capability.stdout]
-type = "wasi:cli"
-inherit-stdout = true
+imports = ["wasip2"]
 
 [capability.wasip2]
 type = "wasi:p2"

examples/interceptor/README.md

@@ -44,13 +44,10 @@ imports = ["stdout-logger"]
 
 [component.stdout-logger]
 uri = "./wasi-logging-to-stdout.wasm"
-imports = ["stdio", "wasip2"]
-
-[capability.stdio]
-uri = "wasmtime:inherit-stdio"
+imports = ["wasip2"]
 
 [capability.wasip2]
-uri = "wasmtime:wasip2"
+type = "wasi:p2"
 ```
 
 ## How It Works

examples/interceptor/config.toml

@@ -10,11 +10,7 @@ imports = ["stdout-logger"]
 uri = "./wasi-logging-to-stdout.wasm"
 # could use this instead of pulling in the build script:
 # uri = "oci://ghcr.io/componentized/logging/to-stdout:v0.2.1"
-imports = ["stdio", "wasip2"]
-
-[capability.stdio]
-type = "wasi:cli"
-inherit-stdio = true
+imports = ["wasip2"]
 
 [capability.wasip2]
 type = "wasi:p2"

examples/otel/README.md

@@ -41,12 +41,12 @@ interface endpoint {
 }
 ```
 
-The endpoint is generic gRPC (OTLP-agnostic, hence the `otel-to-grpc` component). It just sends raw bytes to a named path. Path keys like `logs` and `traces` map to gRPC service paths via config, either in the `host:grpc` capability definition, or the `grpc-to-http` component definition:
+The endpoint is generic gRPC (OTLP-agnostic, hence the `otel-to-grpc` component). It just sends raw bytes to a named path. Path keys like `logs` and `traces` map to gRPC service paths via config, either in the `grpc` capability definition, or the `grpc-to-http` component definition:
 
 ```toml
-config.url = "http://localhost:4317"
-config.paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
-config.paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
+url = "http://localhost:4317"
+paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
+paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
 ```
 
 ## Two Endpoint Options
@@ -67,16 +67,16 @@ uri = "./target/wasm32-wasip2/release/otel_to_grpc.wasm"
 imports = ["grpc", "wasip2"]
 
 [capability.grpc]
-uri = "host:grpc"
-config.url = "http://localhost:4317"
-config.paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
-config.paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
+type = "grpc"
+url = "http://localhost:4317"
+paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
+paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
 
 [capability.wasip2]
-uri = "wasmtime:wasip2"
+type = "wasi:p2"
 ```
 
-The "grpc" definition with `uri = "host:grpc"` creates an instance of the host capability, which the host binary has registered when building the runtime:
+The "grpc" definition creates an instance of the host capability, which the host binary has registered when building the runtime:
 
 ```rust
 let runtime = Runtime::builder()
@@ -105,19 +105,16 @@ imports = ["grpc", "wasip2"]
 
 [component.grpc]
 uri = "./target/wasm32-unknown-unknown/release/grpc_to_http.wasm"
-imports = ["http", "io"]
+imports = ["http"]
 config.url = "http://localhost:4317"
 config.paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
 config.paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
 
 [capability.http]
-uri = "wasmtime:http"
-
-[capability.io]
-uri = "wasmtime:io"
+type = "wasi:http"
 
 [capability.wasip2]
-uri = "wasmtime:wasip2"
+type = "wasi:p2"
 ```
 
 The `grpc-to-http` component constructs a gRPC-framed request and sends it via `wasi:http/outgoing-handler`.

examples/otel/config-with-components.toml

@@ -8,16 +8,13 @@ imports = ["grpc", "wasip2"]
 
 [component.grpc]
 uri = "./target/wasm32-unknown-unknown/release/grpc_to_http.wasm"
-imports = ["http", "io"]
+imports = ["http"]
 config.url = "http://localhost:4317"
 config.paths.logs = "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
 config.paths.traces = "/opentelemetry.proto.collector.trace.v1.TraceService/Export"
 
 [capability.http]
 type = "wasi:http"
 
-[capability.io]
-type = "wasi:io"
-
 [capability.wasip2]
 type = "wasi:p2"

examples/service/README.md

@@ -35,12 +35,12 @@ Result: "HOWDY, World!"
 `GreetingService` implements `Service` with three responsibilities:
 
 1. **Config handling**: A `ConfigHandler` claims the `[greeting]` category, parsing the `message` property. Config is shared with the service via `Arc<Mutex<...>>`.
-2. **Capability provision**: After config is parsed, `capabilities()` uses `.take()` to pull the message out of the mutex and creates a `GreetingCapability` factory. The factory also reads `uppercase` from the capability's `config.*` sub-table.
+2. **Capability provisioning**: After config is parsed, `capabilities()` uses `.take()` to pull the message out of the mutex and creates a `GreetingCapability` factory. The factory also reads `uppercase` from the capability's properties.
 3. **Lifecycle**: `start()` and `shutdown()` are called around invocation.
 
 ## Flow
 
-1. **Configuration**: `[greeting.default]` sets `message = "Howdy"`. `[capability.greeting]` sets `config.uppercase = true`.
+1. **Configuration**: `[greeting.default]` sets `message = "Howdy"`. `[capability.greeting]` sets `uppercase = true`.
 2. **Config phase**: `GreetingConfigHandler` parses the greeting category and stores the message.
 3. **Capability phase**: `GreetingService.capabilities()` takes the stored message, creates a factory that applies the `uppercase` transform.
 4. **Invocation**: Guest calls `get_greeting()`, host returns "HOWDY", guest formats "HOWDY, World!".