Any thin wrapper around the Web Worker API?

Дата публикации: 07-10-2026 15:33:43

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
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Are there wait-free priority queue crates?	0	16.09	05-10-2026
2	Architecture review of a Hyper/Tower-based web framework (Toxi)	0	15.46	06-10-2026
3	Feedback wanted: compio-pool, a thread-per-core connection pool for !Send connections	0	17.89	08-10-2026
4	I built a library for automatic callback encoding/decoding for Teloxide	0	8.24	05-10-2026
5	Rust abstractions for kernel sources	0	4.62	08-10-2026
6	What's everyone working on this week (41/2026)?	0	20.34	06-10-2026
7	Why no Dependent Matrix Type?	0	5.16	08-10-2026
8	Announcing Topcoat: a framework for building full-stack reactive web apps with Rust	0	18.33	22-07-2026
9	Toasty, an async ORM for Rust, is now on crates.io	0	10	03-04-2026
10	Why is f32/f64::sqrt not const?	0	22.72	06-10-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 6.59. Источник: users.rust-lang.org.