Skip to content
Commits on May 24, 2010
  1. Bump version

    committed
  2. Improve MultipartParser test style

    committed
    Now in sync with IncomingForm
  3. Properly declare classes

    committed
    The previous method didn't set obj.constructor.name which is very
    useful to detect an objects class during runtime.
Commits on May 23, 2010
  1. Update readme

    committed
  2. Bump version

    committed
    Also add dep to gently
Commits on May 22, 2010
  1. Use gently for incoming form test

    committed
    Look at all that code going away and becoming much more readable!
Commits on May 20, 2010
  1. Used an actual boundary from firefox for benchmark

    committed
    Looks even nicer now : )
Commits on May 18, 2010
  1. gitignore

    committed
  2. package.json for npm

    committed
  3. A little speed bragging

    committed
  4. Further doc improvements

    committed
  5. License and credits

    committed
  6. Initial documentation

    committed
  7. bytesReceived / bytesExpected

    committed
  8. bytesReceived

    committed
  9. formatting

    committed
  10. Callback for parse

    committed
  11. File upload example

    committed
  12. Parse file uploads properly

    committed
Commits on May 17, 2010
  1. Return the amount of bytes actually parsed

    committed
    Returning 0 isn't all that helpful if we ever have to debug this.
  2. Implemented form.write()

    committed
    Also added better error handling in general (only report 1 error).
  3. Removed ideas dir

    committed
  4. End of stream

    committed
Commits on May 16, 2010
  1. Removed ServerRequest

    committed
    Started work on new IncomingForm class.
Commits on May 7, 2010
  1. Update Makefile to include integration tests

    committed
    Also made the multipart integration test less noisy.
  2. Cleanup test case a little

    committed
  3. Probably final multipart byte skipping algorithm

    committed
    It's not really boyer-moore anymore, and will suck for the worst-case
    scenario. However, best-case performance is really good, easily
    getting 400 mb / sec with a regular-sized boundary.
Commits on May 6, 2010
  1. Bug fix flag setting

    committed
Something went wrong with that request. Please try again.