Lann

Do they need to be methods? Could they just be regular (associated) functions?

I guess bindgen will never generate a `_` prefix so it doesn't really matter :shrug:

Sure, as far I'm concerned! The split between `wasm-tools` and `wit-bindgen` seems pretty arbitrary anyway.

> > Note: Libraries should NOT call set_global_default()! That will cause conflicts when executables try to set them later. `spin_telemetry::init()` is meant to be called by binaries, not libraries. >...

> since it's invoked by clone3() the spin runtime process inherits the global states the shim process has, including global states for the tracing collector. Is this intentional or incidental...

I'm not sure where this behavior is coming from but in general it should be fine to include a default port number in an http host header. If you manually...

Thanks for the update. > It is not overwriting but sending duplicated host header value: This I think may be a bug, but will require some research to understand why...

We have discussed the possibility of adding a "component manifest" format for standalone reusable "library" component projects. It may be that the same idea could serve this purpose as well...

I think the most straightforward way to implement this would be to add new syntax to the `allowed_outbound_hosts` entries, e.g.: ```toml allowed_outbound_hosts = ["(http://host1.com,http://host2.com)"] # which would enable: allowed_outbound_hosts =...

One thing to give a bit of thought to is that this could potentially introduce a kind of variable expansion vulnerability, e.g. ```toml allowed_outbound_hosts = ["(https://production.com,http://localhost:{{dev_port}})"] # Attacker injects SPIN_VARIABLE_DEV_PORT="8000,http://evil.com"...