Search the Community
Showing results for tags 'worker'.
WebWorkers are a way of off-loading tasks from the main browser into a separate thread. ServiceWorkers sit between the browser and the network and extend these capabilities by a couple of powerful features : offline detection and interception possibilities of network requests (fetch api) resource caching under program control (new cacheStorage api) background syncing saving browser apps as icons on the homescreen serving push notifications ServiceWorkers are integral to Progressive Web Apps Architecturally a serviceWorker is just a separate js file, whi
Multi-threading The below approach works. My question though is, is there a simpler solution to the story-line below or is this it ? Computationally intensive tasks can be processed separately from the single thread main js-loop using webworkers. In this case I want to separate an existing processor-intensive procedure (TForm1.TrainNetwork) into its own thread. postMessage is the mechanism which can cross process-space divides and is how the main program and webworkers communicate. This is somewhat different from the CustomEvent mechanism described by Jon in this article.