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
In this case, we might want the same Wasm module to be used in different routes but with different configurations (ie: different WasmMapDir directives, etc.). The reason to use the same Wasm module is to save memory by not loading the same module several times.
The text was updated successfully, but these errors were encountered:
gzurl
changed the title
Support for same Wasm module serving different routes but with different configurations.
Shared Wasm modules with different configurations
Nov 29, 2022
This feature request comes originally from #6.
In this case, we might want the same Wasm module to be used in different routes but with different configurations (ie: different WasmMapDir directives, etc.). The reason to use the same Wasm module is to save memory by not loading the same module several times.
The text was updated successfully, but these errors were encountered: