Skip to content
Commits on Sep 1, 2015
  1. @santigimeno

    v0.2.2

    santigimeno committed
  2. @santigimeno

    src: upgrade to nan2

    santigimeno committed with santigimeno
    Also replace Handle with Local.
    
    PR-URL: #27
    Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Commits on May 5, 2015
  1. v0.2.1

    committed
  2. @santigimeno

    src: only listen read events after writable event

    santigimeno committed with
    - It fixes a regression introduced in version 0.2.0.
    
    Fixes: #24
    PR-URL: #25
    Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
  3. v0.2.0

    committed
    The change in commit 273caec ("src: fix FatalException deprecation
    warning") constitutes a minor API change in that exceptions from
    callbacks now bubble up instead of being treated as fatal errors,
    hence the minor version bump.
  4. test: use assert.equal() instead of plain assert()

    committed
    `assert.equal(a, b)` includes the values in the error message,
    `assert(a === b)` does not.  More context means easier debugging.
  5. src: fix -Wunused-function warnings

    committed
    The SetCloExec() and SetNonBlock() functions are not used on Linux when
    SOCK_CLOEXEC and SOCK_NONBLOCK are available.  Mark them `inline` to
    silence the compiler.
  6. src: fix FatalException deprecation warning

    committed
    The non-isolate version of node::FatalException() has been deprecated
    in io.js; more precisely, it's deprecated in node.js v0.12 as well but
    a bug in joyent/node prevents the deprecation warning from printing.
    
    Switch to NanMakeCallback() because we don't have to catch exceptions
    ourselves.  Exceptions simply unwind the stack until they encounter a
    try/catch block is encountered or the fatal exception handler in the
    io.js or node.js run-time.
    
    Fixes: #23
  7. src: upgrade to nan@1.8.0

    committed
    Fixes build breakage with io.js v2.0.0.
Commits on Mar 17, 2015
  1. v0.1.2

    committed
  2. src: upgrade to nan@1.7.0

    committed
    Fixes build breakage with io.js.
Commits on Jun 4, 2014
  1. v0.1.1

    Rohini Harendra committed
  2. src: Fixing compilation error on node 11

    Rohini Harendra committed
Commits on Jun 3, 2014
  1. v0.1.0

    Rohini Harendra committed
Commits on May 31, 2014
  1. @santigimeno

    src: avoid breaking strict-aliasing rules

    santigimeno committed with santigimeno
    - The compiler was complaining when building the module for node 0.11.13
Commits on May 30, 2014
  1. Merge branch 'santigimeno-nan1.1'

    Rohini Harendra committed
  2. @santigimeno

    src: upgrade to nan@1.1.0

    santigimeno committed with santigimeno
Commits on May 29, 2014
  1. Merge branch 'santigimeno-drain'

    Rohini Harendra committed
  2. @santigimeno

    src: implement socket.connect

    santigimeno committed with santigimeno
    - Implementing connect in dgram sockets allow us to have some kind of flow control
      as we'll receive EAGAIN in case the server buffer is full and a WRITABLE event
      once it's not.
    - Three new events are added:
      · `connect`: if connect succeeds
      · `congestion`: If the server buffer is full
      · `writable`: When the server accepts data again.
    - Add test.
    - Update README.
    - It tries to address bug #4
Commits on May 28, 2014
  1. Merge branch 'santigimeno-return_remote_addr'

    Rohini Harendra committed
Commits on May 25, 2014
  1. @santigimeno

    src: retrieve remote path from received message

    santigimeno committed
    - It's stored in rinfo.path
    - Modify test to cover this case.
Commits on May 20, 2014
  1. @rohiniwork

    Merge pull request #13 from santigimeno/nan1.0

    rohiniwork committed
    Upgrade to nan@1.0.0
Commits on May 17, 2014
  1. @santigimeno

    Upgrade to nan@1.0.0

    santigimeno committed
    - Test pass in 0.11.13, 0.10.28 and 0.8.26
Commits on Mar 22, 2014
  1. src: upgrade to nan 0.8.0

    committed
    Should make it possible to compile against node.js v0.11.12.
    
    Fixes #11.
Commits on Feb 13, 2014
  1. src: fix use after free

    committed
    The memory of the uv_poll_t handle was freed without the handle being
    closed first.  As a result, it was still referenced internally by libuv,
    leading to spurious segmentation faults.  This looks like an oversight
    in the switch from libev to libuv in commit 04dd6d7.
    
    You'd think _I_ of all people would know better, wouldn't you?
    
    Fixes #8.
  2. src: rename sun -> s redux

    committed
    Like commit 05fccae but for another call site.  Overlooked in the
    previous change, mea culpa.
Commits on Jan 7, 2014
  1. src: rename sun -> s

    committed
    @aklt reported compilation errors on Solaris because of a conflicting
    definition of 'sun'.  I've never seen that myself but it doesn't sound
    implausible and it's trivial to change.
    
    Hopefully fixes #7.
  2. src, lib: get rid of js errno global

    committed
    Return error codes directly rather than assigning them to the errno
    JS global.
    
    I made node.js core stop doing that in nodejs/node-v0.x-archive@12d0f0b and then
    some more in nodejs/node-v0.x-archive@ca9eb71, make unix-dgram follow suit.
  3. doc: add README

    committed
    Update Socket#send() in src/unix_dgram.js so it complies with the
    documentation; there is no reason to make the callback mandatory
    so make it optional.
  4. @rvagg
Commits on Sep 16, 2013
  1. src: fix debug build add-on loading

    committed
    Before this commit, the loader in src/unix_dgram.js only looked for the
    release build add-on.  This commit makes it:
    
     * Fall back to the debug build if no release build is found, and
    
     * Removes the node-waf workaround.  Support for node-waf was removed
       in commit e7e3f71 so there is no point in keeping it around.
    
    Fixes #5 and #9.
Commits on Aug 24, 2012
  1. src: don't use ioctl(FIONREAD)

    committed
    On OS X, it always reports that there at least 20 bytes to read.
Commits on Jun 18, 2012
  1. build: remove wscript

    committed
    node 0.7.x and up no longer support node-waf and neither do we.
Something went wrong with that request. Please try again.