web-worker

问题 I'm porting a pile of C++ code to Javascript using the Emscripten system. The C++ code has many calls to fopen which is a synchronous IO call. Within Emscripten, we simulate this using an XHR request to a local resource however , within Firefox synchronous XHR calls (with a responseType of blob or arraybuffer ) are only supported within a Web-Worker. Converting all that c++ code to adapt to asynchronous IO code seems very complicated so for my first try, I'd like to see if I can fake a

问题 I have a script at http://localhost/js/foo.js which needs to spawn a Web Worker from the file http://localhost/js/fooWorker.js . I assumed I could just do something like this: var worker = new Worker('fooWorker.js') However, this results in a 404 error, as the browser cannot find http://localhost/fooWorker.js . I was under the impression that worker paths were resolved relative to the script spawning the worker, so shouldn't I just be able to specify the name of another .js file in the same

问题 I have a first version of using a recursive function with Javascript which produces expected results. Below a working version : // Call the recursive function and get final (a,b) results var HitTemp = JSON.parse(JSON.stringify(HitCurrent)); var result= recursiveFunction(HitTemp, HitTemp.playerCurrent, maxNodes); var a = HitTemp.coordPlayable[0]; var b = HitTemp.coordPlayable[1]; // Recursive function function recursiveFunction(HitCurrent, colorCurrent, depth) { // Indices var i, j, k; //

问题 I am using angular 6. I want to load 100 rows in my grid but this 100rows contains lots of data so while loading this data in my angular application it's hangs the browser. So currently I changed into 20rows per page I am using remote pagination. But I have a requirement to load 100rows in my application. So I tried to implement the WebWorkers. But I didn't find any examples. Can someone give me the example or steps to implement WebWorkers in angular 6 Also I am using reactive formarray for

问题 I am following Angular documentation attempting to try out a basic Web Worker sample. I built a basic Angular template app and it runs fine. I added a very basic component named RunnerComponent and then ran the command (as directed by docs): ng generate web-worker runner That successfully adds the dependencies and adds the new TypeScript file and adds the test code to my RunnerComponent. Here's the simple code it includes in the newly added runner.worker.ts: /// <reference lib="webworker" />

问题 From what I understand, the big benefit of HTML5's shared web workers is that they can accept multiple connections in a single separate thread of execution. My question is: has anyone gotten multiple connections with a SharedWorker to work as a single thread with Google Chrome? I'm using latest version 12.0.742.112. Demo: http://demos.zulius.com/html5/sharedworker Source (in case demo is down): index.html, sharedworker.js The demo establishes 2 separate event listeners. The expected output is

问题 I thought that the serialisation of objects you send with 'postMessage' from a web worker is made with JSON.serialize and the deserialisation with JSON.parse. But I made a test (in Firefox) with that worker code: function A() { this.id = 3; this.save; } var a1 = new A(); var a2 = new A(); a1.save = a2; postMessage({ 'a1' : a1, 'a2' : a2 }); Now in the main file you have that: w.onmessage = function(event) { event.data.a2.id = 7; }; The thing is that the value in a1.save.id is also 7 after

问题 First I have developed much in C#, now I'm working on 3D web project and now the most usable language is JavaScript at the moment. In C# until there becomes the new keywords async/await in new C# specification there was a way to make asynchronous calls by using: delegates Begin/End functions, like: BeginInvoke, EndInvoke IAsync interface As for JS... Right now I have a need to use some parallel computations and really need a stuff, which is similar to asynchronous work with some locking

问题 My intention is for one message to be passed to the worker after it is created, and for that message to be logged by the worker and a reply to be sent back. What happens is that the message sent to the web worker is logged twice, and only one reply is sent. If you refresh the page or pause execution using developer tools, the message is correctly logged once. I created a miniature extension to demonstrate this. There is a background script listening for a click on the browser action button.

问题 I have a React-Native application and I want to use parallel programming (I want to use all of the cores of the tablet). I tried paralleljs and hamsters.js libraries but they were not useful. One doesn't support RN and the other has some issues with Blobs at the moment. So, I decided to use web-workers. After doing some search on it (from MDN etc), I realized that I might use web workers alone instead of all these libraries. However I can't be 100% sure about it. There are other libraries