-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring own FFI Binding for llhttp instead of using http-parser #622
Comments
I agree this has been an ongoing problem. If someone would like to prototype switching to a maintained alternative, that's certainly something we can consider. |
Maybe it would be possible to collaborate with e.g. excon or some of the other ruby http libraries on a shared http parser? |
As for FFI, it looks like @bryanp has suggested it's possible to support with |
Yes, it's possible. I need to find a couple of hours to finish the dual-implementation approach summarized here: bryanp/llhttp#4 (comment). Hoping to get to that in the next couple of weeks. |
It took a bit longer to get to, but |
Thanks @bryanp! |
Hi there, I know there has been talk about dropping http-parser because of it's somewhat staled maintenance state. As I commented on this issue, we experienced segfaults with ruby 2.7 which forced us to dig a bit into the library and dependencies. One issue has already been fixed in ffi and the requirements have been bumped on http-parser, however we still see segfaults even with this new version.
I would love to bring http-parser back to life but even the node community seams to have given up on it:
As stated on the llhttp repository:
Instead of continuing flogging a dead horse, we should probably invest into taking another route. One possible option would be to create a new ffi binding for llhttp. From a quick search I even found a quite recent gem that implements ruby bindings for llhttp, maybe this could be a good candidate to use in the future.
I'm sure that we can come up with some resources to work on this, but I would love to hear your opinion on this topic.
The text was updated successfully, but these errors were encountered: