Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/nodejs/node.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRyan Dahl <ry@tinyclouds.org>2011-07-18 15:36:36 +0400
committerRyan Dahl <ry@tinyclouds.org>2011-07-18 15:36:36 +0400
commitbd2d90feff063f6727de44f623f724f811578c39 (patch)
tree4c3e75216a52e5962dcb5a0545f2d546b0bf0c7a /doc
parent61cda1e34ec8ea779f1a137e86eda81e2d394bae (diff)
Change text on homepage about Web Workers
Diffstat (limited to 'doc')
-rw-r--r--doc/index.html9
1 files changed, 2 insertions, 7 deletions
diff --git a/doc/index.html b/doc/index.html
index 5819f6f78b4..c6ad3c13d61 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -194,13 +194,8 @@ server.listen(1337, "127.0.0.1");
But what about multiple-processor concurrency? Aren't threads
necessary to scale programs to multi-core computers?
</i>
- Processes are necessary to scale to multi-core computers, not
- memory-sharing threads. The fundamentals of scalable systems are
- fast networking and non-blocking design&mdash;the rest is message
- passing. In future versions, Node will be able to fork new
- processes (using the <a
- href="http://www.whatwg.org/specs/web-workers/current-work/"> Web
- Workers API </a>) which fits well into the current design.
+ You can start new processes via <code>child_process.fork()</code>
+ these other processes will be scheduled in parallel.
</p>
<p>