Using batressc’ answer I have managed to actually get passing messages back and forth working, in a somewhat nice manner. Adding to his answer with the libs, the Typescript code also needs some nudges to get working. First, create a file to make the file-loader cooperate with you when importing. I have a file named … Read more
A service worker has additional functionality beyond what’s available in shared workers, and once registered, they persist outside the lifespan of a given web page. Service workers can respond to message events, like shared workers, but they also have access to additional events. Handling fetch events allows service workers to intercept any network traffic (originating … Read more
After seeing this question, I’ve finally implemented sharing socket and added to my library a few days ago. It seems to work in most of browsers including even in IE6, but except Opera. For Opera, you may use regular checking instead of unload event. Check releated issue at https://github.com/flowersinthesand/portal/issues/21 ###Leaving a cookie Set cookie to … Read more
When you create a worker it is actually executed twice. The first pass is in the context of the global ‘window’ object(meaning you have access to all the window object functions). The second call through is in the context of the worker which has a different global object, one where ‘importScripts’ exists. // proper initialization … Read more
Alright, I did some more research with the information @Bergi provided and found the following discussion on W3C mailing list: http://w3-org.9356.n7.nabble.com/Limited-DOM-in-Web-Workers-td44284.html And the excerpt that answers why there is no access to the XML parser or DOM parser in the Web Worker: You’re assuming that none of the DOM implementation code uses any sort of … Read more
Web Workers don’t have a window object. To access global state, use self instead, code that will work on both the main thread and the worker thread. But note that you still won’t be able to access or manipulate the parent DOM (e.g. get window.jQuery via self.jQuery). While the main thread window self points to … Read more
I have created a proper benchmark for that on jsperf. Depending on the browser, WebWorker approach is 85-95% slower than a raw ajax call. Notes: since network response time can be different for each request, I’m testing only new XMLHttpRequest() and JSON.parse(jsonString);. There are no real AJAX calls being made. WebWorker setup and teardown operations … Read more
UPDATE Modern versions of Chrome, Edge, and Firefox now support SharedArrayBuffers (though not safari at the time of this writing see SharedArrayBuffers on MDN), so that would be another possibility for a fast transfer of data with a different set of trade offs compared to a transferrable (you can see MDN for all the trade … Read more
Agreed things would be a lot nicer, but it’s not too hard to hack up a primitive console.log using postMessage. David Flanagan has a nice wrapper here.
There are a few reasons why the error that you mention could have been thrown, the reasons are listed here. When sending objects to web workers, the object is serialized, and later deserialized in the web worker if the object is a serializable object. This means that the methods for the objects you send to … Read more