WASM version running as a service worker?

[pjebs]

How does the WASM version work?

Once you compile it on the server and download it, do you run it inside a service-worker?
If so, how do you keep the service-worker alive?

[x1unix]

@pjebs see #429

[pjebs]

@x1unix It mentions that you are compiling to WASM build on a server. I already knew that part (I think you told me in a different discussion). I also knew you were running the WASM application on the browser.

My question is are you running the WASM build in a JS Service-worker? If so, how are you keeping it alive because Chrome shuts them down when they are idle.

[x1unix]

@pjebs please check the Frontend part of the reply. It directly points to JS piece that executes Go program.

WASM is executed in Web Worker (not to be confused with Service Worker which is a separate thing).
Web worker shuts down right after Go program execution is finished.

This is done to avoid any memory leaks, deadlocks or any other issues.

[pjebs]

Ah i see. I'm trying to run it as a service-worker. Thanks @x1unix