Skip to content
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.

Convert htparse to httparser (we lost the parser war) #7

Closed
NathanFrench opened this issue May 22, 2017 · 2 comments
Closed

Convert htparse to httparser (we lost the parser war) #7

NathanFrench opened this issue May 22, 2017 · 2 comments
Assignees

Comments

@NathanFrench
Copy link
Collaborator

Now that the parser war is over, let's figure out the best plan of action to replace htparser with httparser.

@NathanFrench NathanFrench self-assigned this May 22, 2017
@NathanFrench NathanFrench added this to the 1.1.12 release milestone May 24, 2017
@NathanFrench NathanFrench changed the title [TODO] Convert htparse to httparser (we lost the parser war) Convert htparse to httparser (we lost the parser war) May 24, 2017
@mannol
Copy link

mannol commented Jul 13, 2017

Great to see this project is being maintained. What's the reason for switch to httparser? Performance, stability, etc?

@NathanFrench
Copy link
Collaborator Author

I'd rather blame obscure code on someone else :)

Silliness aside: I've been going back and forth on this one, last I checked htparser is faster, but probably not as feature-rich as http-parser. Currently I've got bigger fish to fry in this code; doubtful this will be dev/tested anytime soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants