-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
experiment: faster wasm streaming in Rust #21323
Conversation
ext/fetch/wasm_streaming.rs
Outdated
} | ||
|
||
/* XXX: crashes here if module compilation fails */ | ||
wasm_streaming.finish(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressing this in WIP feature:
value: v8::Local<v8::Value>, | ||
mut wasm_streaming: v8::WasmStreaming, | ||
) { | ||
let (url, rid) = match compile_response(scope, value) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should make a call into JS here to do a branding check and extract the stream RID, as this could in theory be created w/a Response that is not sourced from fetch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be mean having two wasm streaming callbacks. One in JS doing the brand check and one for streaming in Rust. I don't think the brand check is actually enforced by wpt.
I like this approach, well done. Let me try to get the task spawner experiment working and we can see how they work together. |
Closing because it's stale and we're tackling WASM imports. Feel free to reopen if you want to rebase and try to land it. |
ref denoland/deno_core#349