You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This makes use of the new `wasmtime_wasi_http::handler::ProxyHandler` utility,
which provides both serial and concurrent instance reuse.
We could hypothetically enable opt-in serial reuse for WASIp2 components as well
using the same pattern (which is what `wasmtime serve` does), but I'll leave
that for a follow-up PR, if desired.
This hard-codes the configuration values (max reuse count = 128, max concurrent
reuse count = 16, idle timeout = 1s) for now. Once we've decided where these
values should be configured (e.g. in the spin.toml manifest, in the runtime
config, or at runtime via the component itself), we can support that. See
WebAssembly/wasi-http#190 for related discussion.
Signed-off-by: Joel Dice <[email protected]>
// These error cases should have been ruled out by this point but belt and braces
337
-
(None,None) => Err(anyhow::anyhow!("Triggers must specify either component or static_response - neither is specified for {}", route_match.raw_route())),
338
-
(Some(_),Some(_)) => Err(anyhow::anyhow!("Triggers must specify either component or static_response - both are specified for {}", route_match.raw_route())),
346
+
(None,None) => Err(anyhow::anyhow!(
347
+
"Triggers must specify either component or static_response - neither is specified for {}",
348
+
route_match.raw_route()
349
+
)),
350
+
(Some(_),Some(_)) => Err(anyhow::anyhow!(
351
+
"Triggers must specify either component or static_response - both are specified for {}",
0 commit comments