Skip to content

Add another goal to design/high-level/Goals.md for fine-grained sandboxing #663

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

Open
lukewagner wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −2
Open

Add another goal to design/high-level/Goals.md for fine-grained sandboxing #663

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions design/high-level/Goals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,12 @@
2. Support the definition of portable, virtualizable, statically-analyzable,
capability-safe, language-agnostic interfaces, especially those being
defined by [WASI].
3. Maintain and enhance WebAssembly's unique value proposition:
3. Support fine-grained sandboxing, where a single application can be composed
of multiple components that each encapsulate their own Core WebAssembly
memory and table state, while still allowing multiple Core WebAssembly
modules running inside the *same* component to freely share memory and table
state.
4. Maintain and enhance WebAssembly's unique value proposition:
* *Language neutrality*: avoid biasing the component model toward just one
language or family of languages.
* *Embeddability*: design components to be embedded in a diverse set of
Expand All @@ -24,7 +29,7 @@
[JS API], [Web API] and [ESM-integration]. Before native support is
implemented, ensure components can be polyfilled in browsers via
Ahead-of-Time compilation to currently-supported browser functionality.
4. Define the component model *incrementally*: starting from a set of
5. Define the component model *incrementally*: starting from a set of
[initial use cases] and expanding the set of use cases over time,
prioritized by feedback and experience.

Expand Down
Loading