mscdex
mscdex
I found the problem... I'll submit a pull request shortly.
At this point I'm only really interested in adding firewall rules and routing and the interface does not seem to be anything out of the ordinary, so I wasn't sure...
This module hasn't been updated to use libuv. It is still using libev/libeio directly, which were deprecated in node v0.8.x and now removed in node v0.10.x.
Just thought I'd say that without this dependency update, modern versions of node are emitting deprecation notices due to `node-fetch` 2.x's use of a `whatwg-url` from 2017 that uses `new...
Yes, IIRC both characters should be allowed.
Also FWIW [rfc7230](https://tools.ietf.org/html/rfc7230) obsoletes [rfc2616](https://tools.ietf.org/html/rfc2616).
It would be interesting to see how much of a difference there would be in using NEON on ARM for the parts that use intrinsics. I might try that this...
Ok I just added an implementation that uses NEON and I see ~13% improvement when testing on an Odroid C2: Before: ``` Benchmark result: Took 29.264072 seconds to run 170857.968750...
FWIW here is my NEON patch on top of this PR as it currently stands: ```diff --- http_parser.c.orig 2017-09-23 16:50:15.330221304 -0400 +++ http_parser.c 2017-09-24 02:01:58.228557556 -0400 @@ -443,7 +443,7 @@...
I've updated my patch a bit. I'm also wondering if the non-SIMD implementation might benefit from a SWAR implementation over the current dual `memchr()` solution?