Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tag: v0.1.0
Commits on Jun 30, 2009
  1. @ry

    bump version

    ry authored
  2. @ry

    Add changelog

    ry authored
  3. @ry

    small cleanups

    ry authored
  4. @ry
  5. @ry
  6. @ry
Commits on Jun 29, 2009
  1. @ry

    Add -m32 flags for compiling on 64bit machines.

    ry authored
    These can be removed after v8 supports x64.
  2. @ry
  3. @ry

    Add new test for node.fs.stat()

    ry authored
  4. @ry
  5. @ry

    Snakecase events .

    ry authored
  6. @ry

    Bad array index in AfterStat()

    ry authored
  7. @ry
Commits on Jun 28, 2009
  1. @ry

    Fix unused variable warnings.

    ry authored
  2. @ry
  3. @ry
  4. @ry
  5. @ry

    Implement Promises for file i/o

    ry authored
  6. @ry

    Add Promise class

    ry authored
  7. @ry

    Remove onEvent compatibility

    ry authored
  8. @ry

    Use EventEmitter for node.Process

    ry authored
  9. @ry

    Use events for all HTTP messages.

    ry authored
    This is a rather large refactor! Mostly for the better side. I've had to
    remove some functionality like req.interrupt(). A lot of other work is left
    messy or incomplete.
  10. @ry

    events for http.Server

    ry authored
  11. @ry

    Further expand EventEmitter to TCP and HTTP

    ry authored
    The constructor for TCP servers can no longer take a connection handler for
    purely technical reasons. (The constructor for EventEmitter is implemented
    in C++ but addListener is in javascript, and I don't want to make too many
    C++ -> Javascript references.) Thus I introduce new constructor methods to
    ease the creation of the servers:
    
      node.tcp.createServer()
      node.http.createServer()
    
    These work almost the same as the old constructors.
    
    In general we're working towards a future where no constructors are
    publicly exposed or take arguments.
    
    The HTTP events like "on_uri" are not yet using the event interface.
    onMessage still is a constructor - but this will change soon.
  12. @ry

    Timers on Events

    ry authored
  13. @ry
Commits on Jun 27, 2009
  1. @ry
  2. @ry

    add irc channel to website

    ry authored
Commits on Jun 26, 2009
  1. @ry

    Add make test-all

    ry authored
  2. @ry
  3. @ry

    Fix issue in 5b7fb10

    ry authored
  4. @ry

    Add failing test. Process spawning loop.

    ry authored
    I think this is the issue Felix Geisendoerfer is reporting:
    http://groups.google.com/group/nodejs/browse_thread/thread/efbae1ec1e67786c
Commits on Jun 24, 2009
  1. @ry

    bump version

    ry authored
  2. @ry
  3. @ry

    bugfix: Properly exit a process.

    ry authored
    This requires that onExit() is not called immediately upon receiving a
    SIGCHLD. There could still be data in the pipez. So, instead just set a
    flag and invoke the pipe watchers.
    
    Sometimes one will not receive an EOF from pipes because the process was
    killed by a SIGTERM, or something. If SIGCHLD has been recved but we are
    getting EAGAIN, the pipez need to be closed too.
Something went wrong with that request. Please try again.