Any thin wrapper around the Web Worker API?
Hi, I'm currently writing some audio decoding pipeline targeting wasm32-unknown-unknown.
In the queue / jittering part, I wanna be able to have one task that pushes data as it comes (with all the network uncertainties), and another parallel task that reads data from this buffer. On a native platform, a naive solution would be to use tokio tasks with a mutex around the buffer. Obviously this is not possible in WASM as-is.
Is there any crate that interfaces with the Web Workers API? The most idiomatic (as in matching the API as opposed to match tokio style) the better.
Thanks!
1 post - 1 participant
原文：https://www.a8q9.cn/en/article/any-thin-wrapper-around-the-web-worker-api-dd1e60.html