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.

Sign up for GitHub

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

Jump to bottom

Expose the WebAssembly runtime to applets #121

Open
ia0 opened this issue Apr 23, 2023 · 0 comments
Open

Expose the WebAssembly runtime to applets #121

ia0 opened this issue Apr 23, 2023 · 0 comments
Labels
crate:api Modifies the applet API crate:scheduler Modifies the platform for:usability Improves users (and maintainers) life needs:design Needs design to make progress prio:low Doesn't have a use case (yet)

Comments

@ia0
Copy link
Member

ia0 commented Apr 23, 2023 •
edited
Loading

Applets may want to run sandboxed code. It would be convenient for them to reuse the WebAssembly runtime of the scheduler. This could be useful for example to execute a policy.

Design questions:

  • The applet would need to provide host functions in some form.
  • Should the new module be executed in the same store as the applet? Probably not.
  • What is the performance cost of starting a new store?
  • Should we run in a different execution context? (related to Unprivileged scheduler #78)
@ia0 ia0 added needs:design Needs design to make progress for:usability Improves users (and maintainers) life crate:scheduler Modifies the platform crate:api Modifies the applet API labels Apr 23, 2023
@ia0 ia0 added the prio:low Doesn't have a use case (yet) label Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crate:api Modifies the applet API crate:scheduler Modifies the platform for:usability Improves users (and maintainers) life needs:design Needs design to make progress prio:low Doesn't have a use case (yet)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ia0