Interesting implementation. I'm note able to tell if it would be complicated to reproduce the JSONPath-like behaviour of JSONStream.
I use it to parse couchDB result sets and it works. But it is SLLOOOWWW On Saturday, 31 May 2014 01:12:13 UTC+2, Bruno Jouhier wrote: > > I just released a first version of i-json, a fast incremental JSON parser: > https://github.com/bjouhier/i-json > > Main features: > > - It is FAST :-), but still slower than JSON.parse :-(. On my bench > (parsing a realistic 8 MB JSON file), it comes out as only 60% slower than > JSON.parse. In comparison, the pure JS parsers that I have tried are more > than 6 times slower than JSON.parse. > - It is incremental and it works directly on buffers (on strings too > :-). So you can call it directly with buffers that you receive through > 'data' events. > - It can work either as a DOM parser or an evented one (less events > than SAX but probably enough). > - API is small. The intent is not to provide a sophisticated API but a > fast engine around which you can build fancier APIs. > - It it implemented in C++ but there is a JS fallback implementation > in case it does not build. the JS implementation is 2.5 to 3 times slower. > I wrote it in JS initially but was not happy with the speed. Both > implementations pass the unit test suite. > > Bruno > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/b7c1012e-3117-4a68-9b69-9154fea5e702%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
