Wasmtime GitHub notifications bot (Jan 20 2025 at 17:19): Wasmtime GitHub notifications bot (Jan 20 2025 at 17:19):mschuwalow opened issue #10051:
Feature
Not sure whether this is intended behaviour, but currently wasmtime serve does not maintain state of the component between different requests (I guess because a new store gets created for each invocation here)
As a user, I would expect it to maintain state between different requests.
Benefit
The proposed behaviour should be more in-line with user expecations. If the current behavior is documented / intended, feel free to close this issue.
Wasmtime GitHub notifications bot (Jan 20 2025 at 19:59):bjorn3 commented on issue #10051:
This is intended. Each request gets served by a separate instance for better security by isolating requests from each other.
Wasmtime GitHub notifications bot (Jan 20 2025 at 20:00):mschuwalow closed issue #10051:
Feature
Not sure whether this is intended behaviour, but currently wasmtime serve does not maintain state of the component between different requests (I guess because a new store gets created for each invocation here)
As a user, I would expect it to maintain state between different requests.
Benefit
The proposed behaviour should be more in-line with user expecations. If the current behavior is documented / intended, feel free to close this issue.
Wasmtime GitHub notifications bot (Jan 20 2025 at 20:00):mschuwalow commented on issue #10051:
that's fair. Closing this issue
Last updated: Jan 24 2025 at 00:11 UTC