-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node should work in Web Workers [$105] #494
Comments
👍 |
This would be very helpful to me. Currently I'm having problems with GUI hanging on computationally heavy stuff. |
This would be awesome! |
We are unzipping large files using adm-zip and our app hangs now. Would be great if we could move this code to webworker. |
+1! |
any news on that or on child_processes? i really need to offload main thread. attaching node executable to app package is not an option. |
I agree: this would be a real nice (and imho needed) feature for doing non-blocking actions like unzipping, encryption, decryption, and so on. Currently i am doing a lot of stuff with HTML5 FileAPI ... |
+10, this would be the single most important feature for me for the next version. Currently https://groups.google.com/forum/#!topic/node-webkit/ZBD3SVKmPSM there is no response :( |
At current I've just taken to packaging node with my app and using child_process.fork. It actually works very nicely. |
var worker = require("child_process").fork("testworker.js", {execPath: "/path/to/included/node"}); |
Ups. Thanks. I did not see that option in the nodejs manual. Thanks for the code. (by the way execPath should point to node.exe I think. Thank you very much for that fast help 👍 |
@gunnar-t it's only .exe on windows - the path he shows is one for a unix-y system. :) |
Oh. Of course. It's been a long day in the office. So it seems half of my brain is already sleeping :) |
Don't code half sleeping either, in my experience that has just as awful of results. ;) |
Yeah, but sometimes funny moments the next time you take a look at your code :) |
any plans for this in 0.7.X? |
Any update if this is still in the works? My app would run better if I could offload some of the heavy weight stuff on another processes. |
@jasonfutch yeah, another interesting thing is that more kinds of web workers is coming, like ServiceWorkers and SharedWorkers, so it would be great to solve that issue ASAP. |
this would be a killer feature! |
huge +1. |
+1 |
+1 |
1 similar comment
+1 |
+1!!!!!!! |
+1 |
This would be huge, just added to the bounty! |
+1 |
2 similar comments
+1 |
+1 |
m endoooooooooooooooooooooooooooooooooorsss >:o Le 12/08/2014 14:09, Felipe a écrit ::'(
|
What is the status on this? |
Any news on this? Or other workarounds? |
Really interested in this too :) /cc @rogerwang |
For what it's worth |
The issue is windows specific. Thanks, Regards, Sharique
|
@shabeepk I've just been able to test things on two windows machines (7 and 8) and |
How does the bountysource thing work? Can I +1 this feature and add 5$ or something? |
|
@lcb931023 regarding (2): I've not encountered any issues with |
@makeusabrew haha good to know, thanks, will keep an eye out |
Node.js is now supported in Web Workers. The feature is now in git and will be released with 0.18.4 soon. If you find any bug about the feature, please do NOT follow up here, file a new issue instead. |
It's built here: http://dl.nwjs.io/live-build/10-28-2016/nw18-64d2849-1d4579d-ae7e389-41840a3/v0.18.4/ You need to use '--enable-node-worker' to turn on this feature. |
docs commit: 226c356 |
There is a $105 open bounty on this issue. Add to the bounty at Bountysource.
The text was updated successfully, but these errors were encountered: