Allusion VS comlink

Allusion? https://github.com/allusion-app/Allusion

You can only block a web worker thread; blocking in the main thread is not allowed by browser vendors. If you want to synchronize two web workers, you can use the std primitives like Mutex and compile with atomics. If you want to synchronize the main thread and a web worker, you need to build this yourself. I have implemented this in one of my code bases (https://github.com/allusion-app/Allusion/blob/master/wasm/masonry/src/sync.rs) but the code is GPL licensed. Note this particular code only works in browsers that support Atomics.waitAsync. An alternative is to wrap a worker.onmessage callback in a Promise and await that. Also statics are used because I don't want the overhead of calling receive from JavaScript back to Rust in the web worker, not that they are required.

One idea that could work out is to move state management to a web worker and state changes are just messages between the main thread and web worker (JS example with Redux + React + Comlink. The Redux and Comlink would be reimplemented in Rust (requires atomics, WASM intrinsics and however Redux works). However, using atomics is not so nice. Atomic.waitAsync has so far been only stabilized in Chrome last time I used it and the Rust std library has no equivalent, so you still have to call that from Rust. I've implemented something similar to a channel/spinlock but with statics (github source).

The final implementation: Masonry algorithm in Rust, Webworker, Masonry renderer which makes use of the Virtualized renderer

Feels like taking a general Comlink-like system & making it more component oriented. Good ideas. https://github.com/GoogleChromeLabs/comlink

React UI Framework: https://ant.design/ Reactive: https://www.learnrxjs.io/ Workers: https://github.com/GoogleChromeLabs/comlink Graphics: https://www.pixijs.com/

Reminds me of Comlink

Now that we have a way to create PDF files, we can create a web worker to run the renderPDF function in a separate thread. Here’s an example of a web worker that uses comlink to expose the renderPDF function as an asynchronous function:

To streamline the process of configuring the Service Worker and simplify communication between the app and the Service Worker, we will be using the comlink library.

While there's no realistic way to provide a security boundary between JavaScript modules, Workers are a possibility [1].

The code with the more restricted set of permissions must run in the Worker. That code then communicates with the rest of your app through postMessage / SharedArrayBuffer, perhaps using ComLink [2].

[1] https://deno.land/[email protected]/runtime/workers#specifying-...

[2] https://github.com/GoogleChromeLabs/comlink

The worker API is very simple, you would post a message to the worker. The worker would have the code to process and reply back with the results to the listeners. To make it even easier Google has created the comlink library.