Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upWASM version #18
Closed
WASM version #18
Conversation
|
Maybe we should just keep this in a branch to avoid people picking it by accident until we have a use case for it? The only use case I knew was in case it was faster than the node wrapper. |
|
Agreed we should keep it in a branch until decided otherwise - could be a useful execution target for some scenarios, but not needed for us |
|
One suggested use case is to inject into pages as a service worker on iOS, so that iOS can take advantage of (among other things) uBO style request proxying / rewriting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
AndriusA commentedMay 17, 2019
Basic WASM module to create a blocking engine and check urls against network rules.
From benchmarks appears to be slower (more than 40%) than just Rust-neon based node native wrapper