Skip to content
Commits on Apr 4, 2014
  1. @mcavage

    v0.7.1

    mcavage committed Apr 4, 2014
  2. @pfmooney

    Merge pfmooney/parser-error-handling

    * pfmooney/parser-error-handling:
      Improve parser error handling
    pfmooney committed Apr 4, 2014
  3. @mcavage

    #169: dependency updates

    mcavage committed Apr 4, 2014
Commits on Apr 2, 2014
  1. @mcavage

    Merge pull request #173 from evanshortiss/master

    Make dtrace-provider an optional dependency
    mcavage committed Apr 2, 2014
  2. @evanshortiss
  3. @evanshortiss

    Fix DTraceProvider name

    evanshortiss committed Apr 1, 2014
  4. @evanshortiss
Commits on Mar 15, 2014
  1. @pfmooney

    Improve parser error handling

    In cases where one side of the connection is not communicated with valid
    ASN.1/BER, it would be better to fire an error event rather than let the
    exception bubble all the way up.
    
    Fix mcavage/node-ldapjs#142
    pfmooney committed Mar 15, 2014
Commits on Jan 23, 2014
  1. @pfmooney

    Circumvent lack of 'close' event for tls sockets

    It appears that in node.js (at least recent versions), the 'close' event
    is not emitted by TLS sockets.  The CleartextStream class specifies that
    the 'close' event is optional, so such operation is allowed.  In order
    to compensate, the event can be trapped at the raw net.socket instead.
    
    Fix mcavage/node-ldapjs#161
    pfmooney committed Jan 23, 2014
Commits on Jan 20, 2014
  1. @pfmooney

    Remove buffertools dependency

    pfmooney committed Jan 20, 2014
Commits on Jan 18, 2014
  1. @pfmooney

    Update buffertools dependency

    Buffertools 2.0.1 is required to build on VC2013.
    With the change to v2.x, the buffertools.extend() method must be called
    to mimic the prototype extention behavior of the 1.x versions.
    
    Fix mcavage/node-ldapjs#163
    pfmooney committed Jan 18, 2014
Commits on Jan 17, 2014
  1. @pfmooney
  2. @pfmooney
  3. @mcavage

    travis update

    mcavage committed Jan 17, 2014
  4. @mcavage

    lint/test cleanup

    mcavage committed Jan 17, 2014
  5. @pfmooney

    Fix error event handling for pooled clients

    Do not emit error events if no listeners are present
    pfmooney committed Jan 16, 2014
Commits on Jan 16, 2014
  1. @mcavage

    Merge pull request #159 from gfhuertac/master

    Allow ext request message to have a buffer value
    mcavage committed Jan 16, 2014
Commits on Jan 3, 2014
  1. @gfhuertac
  2. @gfhuertac
Commits on Dec 9, 2013
  1. @mcavage

    version bump

    mcavage committed Dec 9, 2013
Commits on Dec 1, 2013
  1. @pfmooney
  2. @pfmooney

    Update Filter utility functions

    - Write simple tests for multi_test
    - Add get_attr_caseless function for improving Filter.Match
    pfmooney committed Nov 30, 2013
Commits on Nov 28, 2013
  1. @pfmooney
  2. @pfmooney

    Minor update to ClientPool event pass-through

    - Allow event pass-through when performing ClientPool.bind
    - Rename createPool parameter for better readability
    - Fix jsstyle error
    pfmooney committed Nov 28, 2013
Commits on Oct 31, 2013
  1. @pfmooney
Commits on Oct 30, 2013
  1. @pfmooney

    Fix unhandled error during client connection

    Client actions utilizing an EventEmitter may generate unhandled errors,
    especially during initial connection.  Tracking whether the emitter has
    been sent via callback is critical for proper routing of such errors.
    
    Fix mcavage/node-ldapjs#144
    pfmooney committed Oct 25, 2013
  2. @pfmooney
  3. @pfmooney

    Fix jsstyle error

    pfmooney committed Oct 29, 2013
  4. @pfmooney
  5. @pfmooney
Commits on Oct 28, 2013
  1. @mcavage
Commits on Oct 26, 2013
  1. @pfmooney

    Merge pull request #152 from madarche/travis-ci-badge

    Travis CI badge to easily spot when tests fail
    pfmooney committed Oct 25, 2013
Commits on Oct 25, 2013
  1. @madarche
  2. @madarche
  3. @pfmooney

    Fix some ClientPool event handling

    Emit connectTimeout and error events from ClientPool as Client would.
    pfmooney committed Oct 24, 2013
Something went wrong with that request. Please try again.