blob: 6d6bfac6855b4f6e09defe1d2e5cbd7bc77a12b4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
/// !example
/// ## Sending events from a worker thread
///
/// This second example demonstrates how we can use events to communicate from the worker
/// thread to the main thread.
///
/// Like before, we create a thread and we define the fibonacci function:
var Threads = require('webworker-threads');
var t = Threads.create();
function fibo(n) {
return n > 1 ? fibo(n - 1) + fibo(n - 2) : 1;
}
/// Instead of running a single fibonacci computation in the worker thread, we are going to execute a function
/// that computes all fibonacci numbers and emits a `data` event for every number it generates.
///
/// This function runs inside the worker thread so it does not see the `t` variable which belongs to the
/// main thread. But **webworker-threads** sets up a global `thread` variable that the worker thread can use to
/// send events to the main thread.
///
/// Here is our fibonacci generator:
function generateFibos(max) {
for (var i = 1; i <= max; i++) {
thread.emit("data", i, fibo(i));
}
}
/// Note: this is obviously a very inefficient algorithm to generate the sequence of fibonacci numbers.
///
/// Inside the main thread, we set up an event listener for the `data` events emitted by the
/// worker thread:
t.on('data', function(n, result) {
console.log('fibo(' + n + ') = ' + result);
})
/// Now, we are ready to go. We load the two functions into the worker thread
t.eval(fibo);
t.eval(generateFibos);
/// And we run the generator with a callback that will execute when the generator returns from its loop:
t.eval("generateFibos(40)", function(err, result) {
if (err) throw err;
console.log("generator is done!");
t.destroy();
});
/// ### Output
///
/// ```
/// fibo(1) = 1
/// fibo(2) = 2
/// fibo(3) = 3
/// fibo(4) = 5
/// ...
/// fibo(39) = 102334155
/// fibo(40) = 165580141
/// generator is done!
/// ```
|
