3 ms·
You might love evpp instead ASIO. It's just pain to install it but once you do it's a heaven. As for HTTP parsing, llhttp does great job. It however lack multi
by v8dev123 5y ago
You might love evpp instead ASIO. It's just pain to install it but once you do it's a heaven.
As for HTTP parsing, llhttp does great job. It however lack multipart parsing.
- nly 5y agoBoost.Beast has its own HTTP parser[0], during the development of which Vinnie Falco (the principle author of Beast) found many bugs/inconsistencies in Node.js's own parser[1]. Personally I'd rather use this than something based on Node.js http-parser. [0] https://www.boost.org/doc/libs/develop/libs/beast/doc/html/beast/ref/boost__beast__http__parser.html https://www.boost.org/doc/libs/develop/libs/beast/doc/html/b... [1] https://github.com/nodejs/http-parser/issues?q=is%3Aissue+author%3Avinniefalco+ https://github.com/nodejs/http-parser/issues?q=is%3Aissue+au...
- secondcoming 5y agoWe actually use the original node.js parser code (http_parser), which was originally based _I believe_ on the nginx parser. The Node people have since moved on to generating the C parser code with Typescript because the original code was too difficult to maintain (llparse). Like I said, human-readable HTTP needs to die, but it's far too late.
- v8dev123 5y agollhttp different from the original http-parser. It has lesser bugs because it's written in Typescript which transpiled to C and it's faster than the original http-parser