|
|
@ -31,7 +31,7 @@ |
|
|
|
<li><a href="/#download" class="download">Download</a></li> |
|
|
|
<li><a href="/about/" class="about current">About</a></li> |
|
|
|
<li><a href="http://search.npmjs.org/" class="npm">npm Registry</a></li> |
|
|
|
<li><a href="http://nodejs.org/docs/latest/api/index.html" class="docs">Docs</a></li> |
|
|
|
<li><a href="http://nodejs.org/api/index.html" class="docs">Docs</a></li> |
|
|
|
<li><a href="http://blog.nodejs.org" class="blog">Blog</a></li> |
|
|
|
<li><a href="/community/" class="community">Community</a></li> |
|
|
|
<li><a href="/logos/" class="logos">Logos</a></li> |
|
|
@ -102,10 +102,10 @@ console.log('Server running at http://127.0.0.1:1337/');</pre> |
|
|
|
<p>But what about multiple-processor concurrency? Aren't |
|
|
|
threads necessary to scale programs to multi-core computers? |
|
|
|
You can start new processes via <code><a |
|
|
|
href="http://nodejs.org/docs/latest/api/child_process.html#child_process.fork">child_process.fork()</a></code> |
|
|
|
href="http://nodejs.org/api/child_process.html#child_process.fork">child_process.fork()</a></code> |
|
|
|
these other processes will be scheduled in parallel. For load |
|
|
|
balancing incoming connections across multiple processes use |
|
|
|
<a href="http://nodejs.org/docs/latest/api/cluster.html">the |
|
|
|
<a href="http://nodejs.org/api/cluster.html">the |
|
|
|
cluster module</a>.</p> |
|
|
|
|
|
|
|
<p>See also:</p> |
|
|
@ -122,7 +122,7 @@ console.log('Server running at http://127.0.0.1:1337/');</pre> |
|
|
|
<li><a href="/#download">Download</a></li> |
|
|
|
<li><a href="/about/">About</a></li> |
|
|
|
<li><a href="http://search.npmjs.org/">npm Registry</a></li> |
|
|
|
<li><a href="http://nodejs.org/docs/latest/api/index.html">Docs</a></li> |
|
|
|
<li><a href="http://nodejs.org/api/index.html">Docs</a></li> |
|
|
|
<li><a href="http://blog.nodejs.org">Blog</a></li> |
|
|
|
<li><a href="/community/">Community</a></li> |
|
|
|
<li><a href="/logos/">Logos</a></li> |
|
|
|