Switch branches/tags
Commits on Jul 4, 2012
Commits on Jun 20, 2012
  1. Merge pull request #4 from DennisKehrig/master

    baalexander committed Jun 20, 2012
    socket.setTimeout now has an effect for me
Commits on Jun 17, 2012
Commits on Nov 30, 2011
  1. Updates version to 0.1.2.

    baalexander committed Nov 30, 2011
    Fix for node v0.6.x.
Commits on Nov 29, 2011
  1. Fixes multiple callbacks when checking port status.

    baalexander committed Nov 29, 2011
    This is a regression issue after updating from v0.4.x to v0.6.x of Node.
Commits on Nov 18, 2011
  1. Updates to v0.1.1.

    baalexander committed Nov 18, 2011
    Uses the async library and resolves Issue #2 when scanning too many ports.
Commits on Nov 2, 2011
  1. Checks range of ports one at a time.

    baalexander committed Nov 2, 2011
    Uses the [async]( library to conveniently check
    each port serially. This may be slower, but prevents errors related to too many
    open socket connections.
    See Issue #2.
  2. Only returns status of a port after connection closed.

    baalexander committed Nov 2, 2011
    Originally, if trying to immediately connect to a port returned from the status
    check, the socket connection may not have finished closing. Now returns the
    status after the connection has finished closing on the socket.
Commits on Aug 30, 2011
  1. Initial release to NPM.

    baalexander committed Aug 30, 2011
  2. Renames port finding functions for clarity.

    baalexander committed Aug 30, 2011
    The original names of `findAnOpenPort` and `findAClosedPort` were ambiguous.
    While the functions were referring to port status, open could be interpreted as
    available. New functions are `findAPortInUse` and `findAPortNotInUse`. Verbose,
    yes.  I am open to suggestions that keep the same tense and verb usage. So, not
    `findAnAvailablePort` and `findAPortInUse`, for example.
Commits on Aug 29, 2011
  1. Destroys the socket on error instead of end.

    baalexander committed Aug 29, 2011
    When only calling socket.end(), the socket would still respond to timeout
Commits on Aug 11, 2011