Skip to content
This repository
tag: v0.7.7
Fetching contributors…

Cannot retrieve contributors at this time

file 98 lines (83 sloc) 4.291 kb
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 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
<html xmlns="">
    <style type="text/css">
    ul {
      padding: 0;
      margin: 0;
    <link type="image/x-icon" rel="icon" href="favicon.ico" />
    <link type="image/x-icon" rel="shortcut icon" href="favicon.ico" />
    <link type="text/css" rel="stylesheet" href="pipe.css" />
    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
    <title>node v0.4 announcement</title>
    <h2>Second Stable Branch of Node released</h2>

    page detailing API changes between v0.4 and v0.2</a>

    Major changes since v0.2:

      <li> Major overhaul of TLS/SSL system. Previously the binding to
      OpenSSL was heavily interwoven into the socket code. This binding was
      reworked to present each connection as a pair of "streams" instead: a
      duplex encrypted stream and a duplex cleartext stream. The encrypted
      stream is piped to a raw TCP socket using the general purpose
      <code>Stream.prototype.pipe()</code> method. Functionality was
      enhanced and API simplified.

      <li>Simpler HTTP client API with connection pools.

      <li> Cheaper <code>Buffer</code> allocation. Node uses
      <code>Buffer</code> objects in many places - it was noticed that they
      were relatively slow to allocate and difficult to garbage collect. The
      implementation changed to use pure javascript objects instead of
      an <code>ObjectWrap</code> which improved performance.

      <li> With a good amount of experience now, some modifications to the
      module loading system were made to better support package managers.
      In particular, npm was forced to resort to deep symlinks and "shim"
      modules to work around missing features in <code>require()</code>. The main
      changes are:
        <li><code>require()</code> calls realpath. That is,
        it resolves symbolic links. This allows symlinked modules to make
        relative requires.

        <li><code>require()</code> now has a primitive understanding of
        <code>package.json</code>. It looks for the <code>main</code>
        script. This allows <code>require()</code> to work on package
        directories directly.

        <li>A specially named directory, <code>node_modules/</code>, is
        searched in the current directory for any modules. This will
        hopefully encourage programmers to bundle modules rather than
        rely on a global namespace.
      Read more about these features in <a
        module documentation</a>.

      <li> A half-complete but good start a native windows build with MinGW
      is underway by Bert Builder. Build instructions can be found <a
        the wiki</a>.

      <li> Node upgraded to the latest version of V8, <code>v3.1.2</code>.
      This includes much work including V8's new compilation infrastructure
      and a GDB plugin on Linux.
      Read <a
        full V8 ChangeLog</a>.

      <li>A new built-in client for V8's debugger was added to Node. It is
      still very primitive but usable for simple task. There is a <a
        href="">small introduction video</a> and
      some <a

      <li>An <code>os</code> module was added by Brian White which exposes
      a lot of basic but useful system information: <code>os.cpus(),
        os.freemem(), os.totalmem(), os.loadavg()</code>

      <li> And, of course, many of bug fixes. See the


Something went wrong with that request. Please try again.