RubyGems - node-compiler - Versions diffs - 0.9.0 → 0.9.1 - Mend

node-compiler 0.9.0 → 0.9.1

Files changed (11721) hide show

data/vendor/node-v7.2.1/doc/api/documentation.html DELETED

@@ -1,161 +0,0 @@
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8">
-  <title>About this Documentation | Node.js v7.2.1 Documentation</title>
-  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:400,700,400italic">
-  <link rel="stylesheet" href="assets/style.css">
-  <link rel="stylesheet" href="assets/sh.css">
-  <link rel="canonical" href="https://nodejs.org/api/documentation.html">
-</head>
-<body class="alt apidoc" id="api-section-documentation">
-  <div id="content" class="clearfix">
-    <div id="column2" class="interior">
-      <div id="intro" class="interior">
-        <a href="/" title="Go back to the home page">
-          Node.js
-        </a>
-      </div>
-      <ul>
-<li><a class="nav-documentation active" href="documentation.html">About these Docs</a></li>
-<li><a class="nav-synopsis" href="synopsis.html">Usage &amp; Example</a></li>
-</ul>
-<div class="line"></div>
-<ul>
-<li><a class="nav-assert" href="assert.html">Assertion Testing</a></li>
-<li><a class="nav-buffer" href="buffer.html">Buffer</a></li>
-<li><a class="nav-addons" href="addons.html">C/C++ Addons</a></li>
-<li><a class="nav-child_process" href="child_process.html">Child Processes</a></li>
-<li><a class="nav-cluster" href="cluster.html">Cluster</a></li>
-<li><a class="nav-cli" href="cli.html">Command Line Options</a></li>
-<li><a class="nav-console" href="console.html">Console</a></li>
-<li><a class="nav-crypto" href="crypto.html">Crypto</a></li>
-<li><a class="nav-debugger" href="debugger.html">Debugger</a></li>
-<li><a class="nav-dns" href="dns.html">DNS</a></li>
-<li><a class="nav-domain" href="domain.html">Domain</a></li>
-<li><a class="nav-errors" href="errors.html">Errors</a></li>
-<li><a class="nav-events" href="events.html">Events</a></li>
-<li><a class="nav-fs" href="fs.html">File System</a></li>
-<li><a class="nav-globals" href="globals.html">Globals</a></li>
-<li><a class="nav-http" href="http.html">HTTP</a></li>
-<li><a class="nav-https" href="https.html">HTTPS</a></li>
-<li><a class="nav-modules" href="modules.html">Modules</a></li>
-<li><a class="nav-net" href="net.html">Net</a></li>
-<li><a class="nav-os" href="os.html">OS</a></li>
-<li><a class="nav-path" href="path.html">Path</a></li>
-<li><a class="nav-process" href="process.html">Process</a></li>
-<li><a class="nav-punycode" href="punycode.html">Punycode</a></li>
-<li><a class="nav-querystring" href="querystring.html">Query Strings</a></li>
-<li><a class="nav-readline" href="readline.html">Readline</a></li>
-<li><a class="nav-repl" href="repl.html">REPL</a></li>
-<li><a class="nav-stream" href="stream.html">Stream</a></li>
-<li><a class="nav-string_decoder" href="string_decoder.html">String Decoder</a></li>
-<li><a class="nav-timers" href="timers.html">Timers</a></li>
-<li><a class="nav-tls" href="tls.html">TLS/SSL</a></li>
-<li><a class="nav-tty" href="tty.html">TTY</a></li>
-<li><a class="nav-dgram" href="dgram.html">UDP/Datagram</a></li>
-<li><a class="nav-url" href="url.html">URL</a></li>
-<li><a class="nav-util" href="util.html">Utilities</a></li>
-<li><a class="nav-v8" href="v8.html">V8</a></li>
-<li><a class="nav-vm" href="vm.html">VM</a></li>
-<li><a class="nav-zlib" href="zlib.html">ZLIB</a></li>
-</ul>
-<div class="line"></div>
-<ul>
-<li><a class="nav-https-github-com-nodejs-node" href="https://github.com/nodejs/node">GitHub Repo &amp; Issue Tracker</a></li>
-<li><a class="nav-http-groups-google-com-group-nodejs" href="http://groups.google.com/group/nodejs">Mailing List</a></li>
-</ul>
-    </div>
-    <div id="column1" data-id="documentation" class="interior">
-      <header>
-        <h1>Node.js v7.2.1 Documentation</h1>
-        <div id="gtoc">
-          <p>
-            <a href="index.html" name="toc">Index</a> |
-            <a href="all.html">View on single page</a> |
-            <a href="documentation.json">View as JSON</a>
-          </p>
-        </div>
-        <hr>
-      </header>
-      <div id="toc">
-        <h2>Table of Contents</h2>
-        <ul>
-<li><span class="stability_undefined"><a href="#documentation_about_this_documentation">About this Documentation</a></span><ul>
-<li><span class="stability_undefined"><a href="#documentation_stability_index">Stability Index</a></span></li>
-<li><span class="stability_1"><a href="#documentation_json_output">JSON Output</a></span></li>
-<li><span class="stability_undefined"><a href="#documentation_syscalls_and_man_pages">Syscalls and man pages</a></span></li>
-</ul>
-</li>
-</ul>
-      </div>
-      <div id="apicontent">
-        <h1>About this Documentation<span><a class="mark" href="#documentation_about_this_documentation" id="documentation_about_this_documentation">#</a></span></h1>
-<!-- type=misc -->
-<p>The goal of this documentation is to comprehensively explain the Node.js
-API, both from a reference as well as a conceptual point of view.  Each
-section describes a built-in module or high-level concept.</p>
-<p>Where appropriate, property types, method arguments, and the arguments
-provided to event handlers are detailed in a list underneath the topic
-heading.</p>
-<p>Every <code>.html</code> document has a corresponding <code>.json</code> document presenting
-the same information in a structured manner.  This feature is
-experimental, and added for the benefit of IDEs and other utilities that
-wish to do programmatic things with the documentation.</p>
-<p>Every <code>.html</code> and <code>.json</code> file is generated based on the corresponding
-<code>.md</code> file in the <code>doc/api/</code> folder in Node.js&#39;s source tree.  The
-documentation is generated using the <code>tools/doc/generate.js</code> program.
-The HTML template is located at <code>doc/template.html</code>.</p>
-<p>If you find an error in this documentation, please <a href="https://github.com/nodejs/node/issues/new">submit an issue</a>
-or see <a href="https://github.com/nodejs/node/blob/master/CONTRIBUTING.md">the contributing guide</a> for directions on how to submit a patch.</p>
-<h2>Stability Index<span><a class="mark" href="#documentation_stability_index" id="documentation_stability_index">#</a></span></h2>
-<!--type=misc-->
-<p>Throughout the documentation, you will see indications of a section&#39;s
-stability.  The Node.js API is still somewhat changing, and as it
-matures, certain parts are more reliable than others.  Some are so
-proven, and so relied upon, that they are unlikely to ever change at
-all.  Others are brand new and experimental, or known to be hazardous
-and in the process of being redesigned.</p>
-<p>The stability indices are as follows:</p>
-<pre class="api_stability api_stability_0">Stability: 0 - Deprecated
-This feature is known to be problematic, and changes are
-planned.  Do not rely on it.  Use of the feature may cause warnings.  Backwards
-compatibility should not be expected.</pre><pre class="api_stability api_stability_1">Stability: 1 - Experimental
-This feature is subject to change, and is gated by a command line flag.
-It may change or be removed in future versions.</pre><pre class="api_stability api_stability_2">Stability: 2 - Stable
-The API has proven satisfactory. Compatibility with the npm ecosystem
-is a high priority, and will not be broken unless absolutely necessary.</pre><pre class="api_stability api_stability_3">Stability: 3 - Locked
-Only fixes related to security, performance, or bug fixes will be accepted.
-Please do not suggest API changes in this area; they will be refused.</pre><h2>JSON Output<span><a class="mark" href="#documentation_json_output" id="documentation_json_output">#</a></span></h2>
-<pre class="api_stability api_stability_1">Stability: 1 - Experimental</pre><p>Every HTML file in the markdown has a corresponding JSON file with the
-same data.</p>
-<p>This feature was added in Node.js v0.6.12.  It is experimental.</p>
-<h2>Syscalls and man pages<span><a class="mark" href="#documentation_syscalls_and_man_pages" id="documentation_syscalls_and_man_pages">#</a></span></h2>
-<p>System calls like <a href="http://man7.org/linux/man-pages/man2/open.2.html">open(2)</a> and <a href="http://man7.org/linux/man-pages/man2/read.2.html">read(2)</a> define the interface between user programs
-and the underlying operating system. Node functions which simply wrap a syscall,
-like <code>fs.open()</code>, will document that. The docs link to the corresponding man
-pages (short for manual pages) which describe how the syscalls work.</p>
-<p><strong>Caveat:</strong> some syscalls, like <a href="http://man7.org/linux/man-pages/man2/lchown.2.html">lchown(2)</a>, are BSD-specific. That means, for
-example, that <code>fs.lchown()</code> only works on Mac OS X and other BSD-derived systems,
-and is not available on Linux.</p>
-<p>Most Unix syscalls have Windows equivalents, but behavior may differ on Windows
-relative to Linux and OS X. For an example of the subtle ways in which it&#39;s
-sometimes impossible to replace Unix syscall semantics on Windows, see <a href="https://github.com/nodejs/node/issues/4760">Node
-issue 4760</a>.</p>
-      </div>
-    </div>
-  </div>
-  <script src="assets/sh_main.js"></script>
-  <script src="assets/sh_javascript.min.js"></script>
-  <script>highlight(undefined, undefined, 'pre');</script>
-</body>
-</html>

data/vendor/node-v7.2.1/doc/api/domain.html DELETED

@@ -1,503 +0,0 @@
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8">
-  <title>Domain | Node.js v7.2.1 Documentation</title>
-  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:400,700,400italic">
-  <link rel="stylesheet" href="assets/style.css">
-  <link rel="stylesheet" href="assets/sh.css">
-  <link rel="canonical" href="https://nodejs.org/api/domain.html">
-</head>
-<body class="alt apidoc" id="api-section-domain">
-  <div id="content" class="clearfix">
-    <div id="column2" class="interior">
-      <div id="intro" class="interior">
-        <a href="/" title="Go back to the home page">
-          Node.js
-        </a>
-      </div>
-      <ul>
-<li><a class="nav-documentation" href="documentation.html">About these Docs</a></li>
-<li><a class="nav-synopsis" href="synopsis.html">Usage &amp; Example</a></li>
-</ul>
-<div class="line"></div>
-<ul>
-<li><a class="nav-assert" href="assert.html">Assertion Testing</a></li>
-<li><a class="nav-buffer" href="buffer.html">Buffer</a></li>
-<li><a class="nav-addons" href="addons.html">C/C++ Addons</a></li>
-<li><a class="nav-child_process" href="child_process.html">Child Processes</a></li>
-<li><a class="nav-cluster" href="cluster.html">Cluster</a></li>
-<li><a class="nav-cli" href="cli.html">Command Line Options</a></li>
-<li><a class="nav-console" href="console.html">Console</a></li>
-<li><a class="nav-crypto" href="crypto.html">Crypto</a></li>
-<li><a class="nav-debugger" href="debugger.html">Debugger</a></li>
-<li><a class="nav-dns" href="dns.html">DNS</a></li>
-<li><a class="nav-domain active" href="domain.html">Domain</a></li>
-<li><a class="nav-errors" href="errors.html">Errors</a></li>
-<li><a class="nav-events" href="events.html">Events</a></li>
-<li><a class="nav-fs" href="fs.html">File System</a></li>
-<li><a class="nav-globals" href="globals.html">Globals</a></li>
-<li><a class="nav-http" href="http.html">HTTP</a></li>
-<li><a class="nav-https" href="https.html">HTTPS</a></li>
-<li><a class="nav-modules" href="modules.html">Modules</a></li>
-<li><a class="nav-net" href="net.html">Net</a></li>
-<li><a class="nav-os" href="os.html">OS</a></li>
-<li><a class="nav-path" href="path.html">Path</a></li>
-<li><a class="nav-process" href="process.html">Process</a></li>
-<li><a class="nav-punycode" href="punycode.html">Punycode</a></li>
-<li><a class="nav-querystring" href="querystring.html">Query Strings</a></li>
-<li><a class="nav-readline" href="readline.html">Readline</a></li>
-<li><a class="nav-repl" href="repl.html">REPL</a></li>
-<li><a class="nav-stream" href="stream.html">Stream</a></li>
-<li><a class="nav-string_decoder" href="string_decoder.html">String Decoder</a></li>
-<li><a class="nav-timers" href="timers.html">Timers</a></li>
-<li><a class="nav-tls" href="tls.html">TLS/SSL</a></li>
-<li><a class="nav-tty" href="tty.html">TTY</a></li>
-<li><a class="nav-dgram" href="dgram.html">UDP/Datagram</a></li>
-<li><a class="nav-url" href="url.html">URL</a></li>
-<li><a class="nav-util" href="util.html">Utilities</a></li>
-<li><a class="nav-v8" href="v8.html">V8</a></li>
-<li><a class="nav-vm" href="vm.html">VM</a></li>
-<li><a class="nav-zlib" href="zlib.html">ZLIB</a></li>
-</ul>
-<div class="line"></div>
-<ul>
-<li><a class="nav-https-github-com-nodejs-node" href="https://github.com/nodejs/node">GitHub Repo &amp; Issue Tracker</a></li>
-<li><a class="nav-http-groups-google-com-group-nodejs" href="http://groups.google.com/group/nodejs">Mailing List</a></li>
-</ul>
-    </div>
-    <div id="column1" data-id="domain" class="interior">
-      <header>
-        <h1>Node.js v7.2.1 Documentation</h1>
-        <div id="gtoc">
-          <p>
-            <a href="index.html" name="toc">Index</a> |
-            <a href="all.html">View on single page</a> |
-            <a href="domain.json">View as JSON</a>
-          </p>
-        </div>
-        <hr>
-      </header>
-      <div id="toc">
-        <h2>Table of Contents</h2>
-        <ul>
-<li><span class="stability_0"><a href="#domain_domain">Domain</a></span><ul>
-<li><span class="stability_undefined"><a href="#domain_warning_don_t_ignore_errors">Warning: Don&#39;t Ignore Errors!</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_additions_to_error_objects">Additions to Error objects</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_implicit_binding">Implicit Binding</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_explicit_binding">Explicit Binding</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_create">domain.create()</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_class_domain">Class: Domain</a></span><ul>
-<li><span class="stability_undefined"><a href="#domain_domain_run_fn_args">domain.run(fn[, ...args])</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_members">domain.members</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_add_emitter">domain.add(emitter)</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_remove_emitter">domain.remove(emitter)</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_bind_callback">domain.bind(callback)</a></span><ul>
-<li><span class="stability_undefined"><a href="#domain_example">Example</a></span></li>
-</ul>
-</li>
-<li><span class="stability_undefined"><a href="#domain_domain_intercept_callback">domain.intercept(callback)</a></span><ul>
-<li><span class="stability_undefined"><a href="#domain_example_1">Example</a></span></li>
-</ul>
-</li>
-<li><span class="stability_undefined"><a href="#domain_domain_enter">domain.enter()</a></span></li>
-<li><span class="stability_undefined"><a href="#domain_domain_exit">domain.exit()</a></span></li>
-<li><span class="stability_0"><a href="#domain_domain_dispose">domain.dispose()</a></span></li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-      </div>
-      <div id="apicontent">
-        <h1>Domain<span><a class="mark" href="#domain_domain" id="domain_domain">#</a></span></h1>
-<pre class="api_stability api_stability_0">Stability: 0 - Deprecated</pre><p><strong>This module is pending deprecation</strong>. Once a replacement API has been
-finalized, this module will be fully deprecated. Most end users should
-<strong>not</strong> have cause to use this module. Users who absolutely must have
-the functionality that domains provide may rely on it for the time being
-but should expect to have to migrate to a different solution
-in the future.</p>
-<p>Domains provide a way to handle multiple different IO operations as a
-single group.  If any of the event emitters or callbacks registered to a
-domain emit an <code>&#39;error&#39;</code> event, or throw an error, then the domain object
-will be notified, rather than losing the context of the error in the
-<code>process.on(&#39;uncaughtException&#39;)</code> handler, or causing the program to
-exit immediately with an error code.</p>
-<h2>Warning: Don&#39;t Ignore Errors!<span><a class="mark" href="#domain_warning_don_t_ignore_errors" id="domain_warning_don_t_ignore_errors">#</a></span></h2>
-<!-- type=misc -->
-<p>Domain error handlers are not a substitute for closing down your
-process when an error occurs.</p>
-<p>By the very nature of how <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/throw"><code>throw</code></a> works in JavaScript, there is almost
-never any way to safely &quot;pick up where you left off&quot;, without leaking
-references, or creating some other sort of undefined brittle state.</p>
-<p>The safest way to respond to a thrown error is to shut down the
-process.  Of course, in a normal web server, you might have many
-connections open, and it is not reasonable to abruptly shut those down
-because an error was triggered by someone else.</p>
-<p>The better approach is to send an error response to the request that
-triggered the error, while letting the others finish in their normal
-time, and stop listening for new requests in that worker.</p>
-<p>In this way, <code>domain</code> usage goes hand-in-hand with the cluster module,
-since the master process can fork a new worker when a worker
-encounters an error.  For Node.js programs that scale to multiple
-machines, the terminating proxy or service registry can take note of
-the failure, and react accordingly.</p>
-<p>For example, this is not a good idea:</p>
-<pre><code class="lang-js">// XXX WARNING!  BAD IDEA!
-var d = require(&#39;domain&#39;).create();
-d.on(&#39;error&#39;, (er) =&gt; {
-  // The error won&#39;t crash the process, but what it does is worse!
-  // Though we&#39;ve prevented abrupt process restarting, we are leaking
-  // resources like crazy if this ever happens.
-  // This is no better than process.on(&#39;uncaughtException&#39;)!
-  console.log(&#39;error, but oh well&#39;, er.message);
-});
-d.run(() =&gt; {
-  require(&#39;http&#39;).createServer((req, res) =&gt; {
-    handleRequest(req, res);
-  }).listen(PORT);
-});
-</code></pre>
-<p>By using the context of a domain, and the resilience of separating our
-program into multiple worker processes, we can react more
-appropriately, and handle errors with much greater safety.</p>
-<pre><code class="lang-js">// Much better!
-const cluster = require(&#39;cluster&#39;);
-const PORT = +process.env.PORT || 1337;
-if (cluster.isMaster) {
-  // In real life, you&#39;d probably use more than just 2 workers,
-  // and perhaps not put the master and worker in the same file.
-  //
-  // You can also of course get a bit fancier about logging, and
-  // implement whatever custom logic you need to prevent DoS
-  // attacks and other bad behavior.
-  //
-  // See the options in the cluster documentation.
-  //
-  // The important thing is that the master does very little,
-  // increasing our resilience to unexpected errors.
-  cluster.fork();
-  cluster.fork();
-  cluster.on(&#39;disconnect&#39;, (worker) =&gt; {
-    console.error(&#39;disconnect!&#39;);
-    cluster.fork();
-  });
-} else {
-  // the worker
-  //
-  // This is where we put our bugs!
-  const domain = require(&#39;domain&#39;);
-  // See the cluster documentation for more details about using
-  // worker processes to serve requests.  How it works, caveats, etc.
-  const server = require(&#39;http&#39;).createServer((req, res) =&gt; {
-    var d = domain.create();
-    d.on(&#39;error&#39;, (er) =&gt; {
-      console.error(&#39;error&#39;, er.stack);
-      // Note: we&#39;re in dangerous territory!
-      // By definition, something unexpected occurred,
-      // which we probably didn&#39;t want.
-      // Anything can happen now!  Be very careful!
-      try {
-        // make sure we close down within 30 seconds
-        var killtimer = setTimeout(() =&gt; {
-          process.exit(1);
-        }, 30000);
-        // But don&#39;t keep the process open just for that!
-        killtimer.unref();
-        // stop taking new requests.
-        server.close();
-        // Let the master know we&#39;re dead.  This will trigger a
-        // &#39;disconnect&#39; in the cluster master, and then it will fork
-        // a new worker.
-        cluster.worker.disconnect();
-        // try to send an error to the request that triggered the problem
-        res.statusCode = 500;
-        res.setHeader(&#39;content-type&#39;, &#39;text/plain&#39;);
-        res.end(&#39;Oops, there was a problem!\n&#39;);
-      } catch (er2) {
-        // oh well, not much we can do at this point.
-        console.error(&#39;Error sending 500!&#39;, er2.stack);
-      }
-    });
-    // Because req and res were created before this domain existed,
-    // we need to explicitly add them.
-    // See the explanation of implicit vs explicit binding below.
-    d.add(req);
-    d.add(res);
-    // Now run the handler function in the domain.
-    d.run(() =&gt; {
-      handleRequest(req, res);
-    });
-  });
-  server.listen(PORT);
-}
-// This part isn&#39;t important.  Just an example routing thing.
-// You&#39;d put your fancy application logic here.
-function handleRequest(req, res) {
-  switch(req.url) {
-    case &#39;/error&#39;:
-      // We do some async stuff, and then...
-      setTimeout(() =&gt; {
-        // Whoops!
-        flerb.bark();
-      });
-      break;
-    default:
-      res.end(&#39;ok&#39;);
-  }
-}
-</code></pre>
-<h2>Additions to Error objects<span><a class="mark" href="#domain_additions_to_error_objects" id="domain_additions_to_error_objects">#</a></span></h2>
-<!-- type=misc -->
-<p>Any time an <code>Error</code> object is routed through a domain, a few extra fields
-are added to it.</p>
-<ul>
-<li><code>error.domain</code> The domain that first handled the error.</li>
-<li><code>error.domainEmitter</code> The event emitter that emitted an <code>&#39;error&#39;</code> event
-with the error object.</li>
-<li><code>error.domainBound</code> The callback function which was bound to the
-domain, and passed an error as its first argument.</li>
-<li><code>error.domainThrown</code> A boolean indicating whether the error was
-thrown, emitted, or passed to a bound callback function.</li>
-</ul>
-<h2>Implicit Binding<span><a class="mark" href="#domain_implicit_binding" id="domain_implicit_binding">#</a></span></h2>
-<!--type=misc-->
-<p>If domains are in use, then all <strong>new</strong> EventEmitter objects (including
-Stream objects, requests, responses, etc.) will be implicitly bound to
-the active domain at the time of their creation.</p>
-<p>Additionally, callbacks passed to lowlevel event loop requests (such as
-to fs.open, or other callback-taking methods) will automatically be
-bound to the active domain.  If they throw, then the domain will catch
-the error.</p>
-<p>In order to prevent excessive memory usage, Domain objects themselves
-are not implicitly added as children of the active domain.  If they
-were, then it would be too easy to prevent request and response objects
-from being properly garbage collected.</p>
-<p>If you <em>want</em> to nest Domain objects as children of a parent Domain,
-then you must explicitly add them.</p>
-<p>Implicit binding routes thrown errors and <code>&#39;error&#39;</code> events to the
-Domain&#39;s <code>&#39;error&#39;</code> event, but does not register the EventEmitter on the
-Domain, so <a href="#domain_domain_dispose"><code>domain.dispose()</code></a> will not shut down the EventEmitter.
-Implicit binding only takes care of thrown errors and <code>&#39;error&#39;</code> events.</p>
-<h2>Explicit Binding<span><a class="mark" href="#domain_explicit_binding" id="domain_explicit_binding">#</a></span></h2>
-<!--type=misc-->
-<p>Sometimes, the domain in use is not the one that ought to be used for a
-specific event emitter.  Or, the event emitter could have been created
-in the context of one domain, but ought to instead be bound to some
-other domain.</p>
-<p>For example, there could be one domain in use for an HTTP server, but
-perhaps we would like to have a separate domain to use for each request.</p>
-<p>That is possible via explicit binding.</p>
-<p>For example:</p>
-<pre><code class="lang-js">// create a top-level domain for the server
-const domain = require(&#39;domain&#39;);
-const http = require(&#39;http&#39;);
-const serverDomain = domain.create();
-serverDomain.run(() =&gt; {
-  // server is created in the scope of serverDomain
-  http.createServer((req, res) =&gt; {
-    // req and res are also created in the scope of serverDomain
-    // however, we&#39;d prefer to have a separate domain for each request.
-    // create it first thing, and add req and res to it.
-    var reqd = domain.create();
-    reqd.add(req);
-    reqd.add(res);
-    reqd.on(&#39;error&#39;, (er) =&gt; {
-      console.error(&#39;Error&#39;, er, req.url);
-      try {
-        res.writeHead(500);
-        res.end(&#39;Error occurred, sorry.&#39;);
-      } catch (er) {
-        console.error(&#39;Error sending 500&#39;, er, req.url);
-      }
-    });
-  }).listen(1337);
-});
-</code></pre>
-<h2>domain.create()<span><a class="mark" href="#domain_domain_create" id="domain_domain_create">#</a></span></h2>
-<div class="signature"><ul>
-<li>return: <span class="type">&lt;Domain&gt;</span></li>
-</ul>
-</div><p>Returns a new Domain object.</p>
-<h2>Class: Domain<span><a class="mark" href="#domain_class_domain" id="domain_class_domain">#</a></span></h2>
-<p>The Domain class encapsulates the functionality of routing errors and
-uncaught exceptions to the active Domain object.</p>
-<p>Domain is a child class of <a href="events.html#events_class_eventemitter"><code>EventEmitter</code></a>.  To handle the errors that it
-catches, listen to its <code>&#39;error&#39;</code> event.</p>
-<h3>domain.run(fn[, ...args])<span><a class="mark" href="#domain_domain_run_fn_args" id="domain_domain_run_fn_args">#</a></span></h3>
-<div class="signature"><ul>
-<li><code>fn</code> <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function" class="type">&lt;Function&gt;</a></li>
-<li><code>...args</code> <span class="type">&lt;any&gt;</span></li>
-</ul>
-</div><p>Run the supplied function in the context of the domain, implicitly
-binding all event emitters, timers, and lowlevel requests that are
-created in that context. Optionally, arguments can be passed to
-the function.</p>
-<p>This is the most basic way to use a domain.</p>
-<p>Example:</p>
-<pre><code class="lang-js">const domain = require(&#39;domain&#39;);
-const fs = require(&#39;fs&#39;);
-const d = domain.create();
-d.on(&#39;error&#39;, (er) =&gt; {
-  console.error(&#39;Caught error!&#39;, er);
-});
-d.run(() =&gt; {
-  process.nextTick(() =&gt; {
-    setTimeout(() =&gt; { // simulating some various async stuff
-      fs.open(&#39;non-existent file&#39;, &#39;r&#39;, (er, fd) =&gt; {
-        if (er) throw er;
-        // proceed...
-      });
-    }, 100);
-  });
-});
-</code></pre>
-<p>In this example, the <code>d.on(&#39;error&#39;)</code> handler will be triggered, rather
-than crashing the program.</p>
-<h3>domain.members<span><a class="mark" href="#domain_domain_members" id="domain_domain_members">#</a></span></h3>
-<div class="signature"><ul>
-<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array" class="type">&lt;Array&gt;</a></li>
-</ul>
-</div><p>An array of timers and event emitters that have been explicitly added
-to the domain.</p>
-<h3>domain.add(emitter)<span><a class="mark" href="#domain_domain_add_emitter" id="domain_domain_add_emitter">#</a></span></h3>
-<div class="signature"><ul>
-<li><code>emitter</code> <a href="events.html#events_class_eventemitter" class="type">&lt;EventEmitter&gt;</a> | <a href="timers.html#timers_timers" class="type">&lt;Timer&gt;</a> emitter or timer to be added to the domain</li>
-</ul>
-</div><p>Explicitly adds an emitter to the domain.  If any event handlers called by
-the emitter throw an error, or if the emitter emits an <code>&#39;error&#39;</code> event, it
-will be routed to the domain&#39;s <code>&#39;error&#39;</code> event, just like with implicit
-binding.</p>
-<p>This also works with timers that are returned from <a href="timers.html#timers_setinterval_callback_delay_args"><code>setInterval()</code></a> and
-<a href="timers.html#timers_settimeout_callback_delay_args"><code>setTimeout()</code></a>.  If their callback function throws, it will be caught by
-the domain &#39;error&#39; handler.</p>
-<p>If the Timer or EventEmitter was already bound to a domain, it is removed
-from that one, and bound to this one instead.</p>
-<h3>domain.remove(emitter)<span><a class="mark" href="#domain_domain_remove_emitter" id="domain_domain_remove_emitter">#</a></span></h3>
-<div class="signature"><ul>
-<li><code>emitter</code> <a href="events.html#events_class_eventemitter" class="type">&lt;EventEmitter&gt;</a> | <a href="timers.html#timers_timers" class="type">&lt;Timer&gt;</a> emitter or timer to be removed from the domain</li>
-</ul>
-</div><p>The opposite of <a href="#domain_domain_add_emitter"><code>domain.add(emitter)</code></a>.  Removes domain handling from the
-specified emitter.</p>
-<h3>domain.bind(callback)<span><a class="mark" href="#domain_domain_bind_callback" id="domain_domain_bind_callback">#</a></span></h3>
-<div class="signature"><ul>
-<li><code>callback</code> <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function" class="type">&lt;Function&gt;</a> The callback function</li>
-<li>return: <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function" class="type">&lt;Function&gt;</a> The bound function</li>
-</ul>
-</div><p>The returned function will be a wrapper around the supplied callback
-function.  When the returned function is called, any errors that are
-thrown will be routed to the domain&#39;s <code>&#39;error&#39;</code> event.</p>
-<h4>Example<span><a class="mark" href="#domain_example" id="domain_example">#</a></span></h4>
-<pre><code class="lang-js">const d = domain.create();
-function readSomeFile(filename, cb) {
-  fs.readFile(filename, &#39;utf8&#39;, d.bind((er, data) =&gt; {
-    // if this throws, it will also be passed to the domain
-    return cb(er, data ? JSON.parse(data) : null);
-  }));
-}
-d.on(&#39;error&#39;, (er) =&gt; {
-  // an error occurred somewhere.
-  // if we throw it now, it will crash the program
-  // with the normal line number and stack message.
-});
-</code></pre>
-<h3>domain.intercept(callback)<span><a class="mark" href="#domain_domain_intercept_callback" id="domain_domain_intercept_callback">#</a></span></h3>
-<div class="signature"><ul>
-<li><code>callback</code> <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function" class="type">&lt;Function&gt;</a> The callback function</li>
-<li>return: <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function" class="type">&lt;Function&gt;</a> The intercepted function</li>
-</ul>
-</div><p>This method is almost identical to <a href="#domain_domain_bind_callback"><code>domain.bind(callback)</code></a>.  However, in
-addition to catching thrown errors, it will also intercept <a href="errors.html#errors_class_error"><code>Error</code></a>
-objects sent as the first argument to the function.</p>
-<p>In this way, the common <code>if (err) return callback(err);</code> pattern can be replaced
-with a single error handler in a single place.</p>
-<h4>Example<span><a class="mark" href="#domain_example_1" id="domain_example_1">#</a></span></h4>
-<pre><code class="lang-js">const d = domain.create();
-function readSomeFile(filename, cb) {
-  fs.readFile(filename, &#39;utf8&#39;, d.intercept((data) =&gt; {
-    // note, the first argument is never passed to the
-    // callback since it is assumed to be the &#39;Error&#39; argument
-    // and thus intercepted by the domain.
-    // if this throws, it will also be passed to the domain
-    // so the error-handling logic can be moved to the &#39;error&#39;
-    // event on the domain instead of being repeated throughout
-    // the program.
-    return cb(null, JSON.parse(data));
-  }));
-}
-d.on(&#39;error&#39;, (er) =&gt; {
-  // an error occurred somewhere.
-  // if we throw it now, it will crash the program
-  // with the normal line number and stack message.
-});
-</code></pre>
-<h3>domain.enter()<span><a class="mark" href="#domain_domain_enter" id="domain_domain_enter">#</a></span></h3>
-<p>The <code>enter</code> method is plumbing used by the <code>run</code>, <code>bind</code>, and <code>intercept</code>
-methods to set the active domain. It sets <code>domain.active</code> and <code>process.domain</code>
-to the domain, and implicitly pushes the domain onto the domain stack managed
-by the domain module (see <a href="#domain_domain_exit"><code>domain.exit()</code></a> for details on the domain stack). The
-call to <code>enter</code> delimits the beginning of a chain of asynchronous calls and I/O
-operations bound to a domain.</p>
-<p>Calling <code>enter</code> changes only the active domain, and does not alter the domain
-itself. <code>enter</code> and <code>exit</code> can be called an arbitrary number of times on a
-single domain.</p>
-<p>If the domain on which <code>enter</code> is called has been disposed, <code>enter</code> will return
-without setting the domain.</p>
-<h3>domain.exit()<span><a class="mark" href="#domain_domain_exit" id="domain_domain_exit">#</a></span></h3>
-<p>The <code>exit</code> method exits the current domain, popping it off the domain stack.
-Any time execution is going to switch to the context of a different chain of
-asynchronous calls, it&#39;s important to ensure that the current domain is exited.
-The call to <code>exit</code> delimits either the end of or an interruption to the chain
-of asynchronous calls and I/O operations bound to a domain.</p>
-<p>If there are multiple, nested domains bound to the current execution context,
-<code>exit</code> will exit any domains nested within this domain.</p>
-<p>Calling <code>exit</code> changes only the active domain, and does not alter the domain
-itself. <code>enter</code> and <code>exit</code> can be called an arbitrary number of times on a
-single domain.</p>
-<p>If the domain on which <code>exit</code> is called has been disposed, <code>exit</code> will return
-without exiting the domain.</p>
-<h3>domain.dispose()<span><a class="mark" href="#domain_domain_dispose" id="domain_domain_dispose">#</a></span></h3>
-<pre class="api_stability api_stability_0">Stability: 0 - Deprecated.  Please recover from failed IO actions
-explicitly via error event handlers set on the domain.</pre><p>Once <code>dispose</code> has been called, the domain will no longer be used by callbacks
-bound into the domain via <code>run</code>, <code>bind</code>, or <code>intercept</code>, and a <code>&#39;dispose&#39;</code> event
-is emitted.</p>
-      </div>
-    </div>
-  </div>
-  <script src="assets/sh_main.js"></script>
-  <script src="assets/sh_javascript.min.js"></script>
-  <script>highlight(undefined, undefined, 'pre');</script>
-</body>
-</html>