Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shared Wasm modules with different configurations #7

Closed
gzurl opened this issue Oct 18, 2022 · 1 comment
Closed

Shared Wasm modules with different configurations #7

gzurl opened this issue Oct 18, 2022 · 1 comment
Assignees
Labels
🚀 enhancement New feature or request

Comments

@gzurl
Copy link
Contributor

gzurl commented Oct 18, 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.

@gzurl gzurl added the 🚀 enhancement New feature or request label Oct 18, 2022
@gzurl gzurl self-assigned this Nov 11, 2022
gzurl added a commit that referenced this issue Nov 25, 2022
Multi-module and Multi-configuration support. Fixes #6, #7, and #16.
@gzurl
Copy link
Contributor Author

gzurl commented Nov 25, 2022

Fixed at #27

@gzurl gzurl closed this as completed Nov 25, 2022
@gzurl 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant