Node.js HTTP relies on llhttp parser, which is a both a semi-obscure piece of code and semi-abandoned project.
As the parser is a critical part of Node.js, do we have better alternatives for easier maintainability? Let's find out.
Session facilitator(s), Github handle(s) and timezone(s)
Paolo Insogna (@ShogunPanda) - CEST (but will be in Vancouver)
Proposal
Topic of the session
Node.js HTTP parser, what's going on?
Type of the session
Estimated duration of the session
30min + Q/A and or discussion
Date and Time of the session
TBD
Level
Pre-requisite knowledge
Node.js internal HTTP stack knowledge
Describe the session
Node.js HTTP relies on llhttp parser, which is a both a semi-obscure piece of code and semi-abandoned project. As the parser is a critical part of Node.js, do we have better alternatives for easier maintainability? Let's find out.
Session facilitator(s), Github handle(s) and timezone(s)
Paolo Insogna (@ShogunPanda) - CEST (but will be in Vancouver)
Meeting notes and Virtual Meeting Link
TBD
Follow-up / Set-up sessions (if any)
TBD