Skip to content
Commits on Jan 31, 2012
  1. Version 0.1.0

    committed Jan 31, 2012
Commits on Jan 30, 2012
  1. Merge pull request #4 from mattbornski/master

    RFC 5424 format requires months indexed from [1, 12] but Javascript Date objects represent months indexed from [0, 11]
    committed Jan 30, 2012
  2. @mattbornski

    RFC 5424 format requires months indexed from [1, 12] but Javascript D…

    …ate objects represent months indexed from [0, 11]
    mattbornski committed Jan 30, 2012
  3. Merge pull request #3 from mattbornski/master

    Validate facility in FacilityIndex, not SeverityIndex
    committed Jan 30, 2012
  4. @mattbornski
Commits on Dec 9, 2011
  1. Version 0.0.9

    committed Dec 9, 2011
  2. Merge pull request #2 from artifi/master

    Small bugfix for dateObject creation.
    committed Dec 9, 2011
  3. @artifi
Commits on Nov 28, 2011
  1. Adding a basic perf set for testing the parser

    This is pretty basic and will generate logs for each individual test - drilling
    them down like this let's me help get at particular parts being executed like
    the date or structured data. I'll eventually make a helper to collate and
    display the data...
    committed Nov 28, 2011
  2. Leaving notes for areas of potential performance improvement

    The profiling has shown that wildcard regexes and split based regexes are the
    biggest causes of inefficient code - however for some such as date parsing I
    can't think of a better way of handling it at this point in time.
    committed Nov 28, 2011
  3. Replacing a time consuming regex within the parser

    Initial profiling of the code is showing that this regex based split is taking
    more than it's fair share of time. As a side penalty this could cause issues
    with messages having > 1 spaces as delimitered (although that's RFC violating).
    committed Nov 28, 2011
  4. Version 0.0.8

    committed Nov 28, 2011
  5. Updating README

    committed Nov 28, 2011
  6. Enabling auto handling of signed blocks and certs

    I am somewhat divided by this commit, although it preserves all data it parses,
    it ends up making a object that's huge and too full of redundancy. I may end up
    "replacing" all of SDDATA with our parsed signed block instead of this.
    committed Nov 28, 2011
  7. Adding basic support for signed certificate messages

    Like the previous, signed block commit many of the same things
    apply: we don't touch and of the crypto apart from attempting
    to take it out from it's base64 state.
    committed Nov 28, 2011
Commits on Nov 27, 2011
  1. Minor documentation fixes

    committed Nov 27, 2011
  2. Adding basic parser handling for signed block messages.

    At this stage, supporting the validation of messages in terms of checksum and
    signature matching is not feasible because of the requirement to comply with RFC
    4880. Since we at least give back buffer objects, end users can handle that
    themselves a little easier.
    committed Nov 27, 2011
Commits on Nov 25, 2011
  1. Rewritten the structured data parser.

    The previous implementation did not handle = characters, used by Base64 encoded
    payloads for signed (RFC5848) message correctly, breaking all over the place.
    This rewrite attempts to be stricter in compliance to the spec.
    committed Nov 25, 2011
Commits on Nov 23, 2011
  1. Version 0.0.7

    committed Nov 23, 2011
  2. Adding test for structured data

    committed Nov 23, 2011
  3. Fixing producer tests

    committed Nov 23, 2011
  4. Complete rewrite of producer and clearup of tests.

    This commit brings in structured data support for RFC5424 and, more importantly,
    a much cleaner producer removing a lot of silly code. We also accept all fields
    that are possible to be filled in, and default appropriately when they are
    empty.
    
    In addition to this, the BSD style tests have been rewritten to be more inline
    with the RFC.
    committed Nov 23, 2011
  5. Whitespace cleanup

    committed Nov 23, 2011
  6. Minor whitespace cleanup

    committed Nov 23, 2011
  7. procID really just should be pid

    committed Nov 23, 2011
  8. Version 0.0.6

    committed Nov 23, 2011
  9. Updating documentation

    committed Nov 23, 2011
Something went wrong with that request. Please try again.