-
Notifications
You must be signed in to change notification settings - Fork 327
Closed
Description
I'm looking at the history and can't find out why the FFI version is required. https://github.com/bryanp/llhttp/ states
This is a monorepo that includes projects for MRI and FFI. Generally speaking, you should prefer the MRI version and fallback to the FFI version for better compatibility. There is parity between the two implementations, but the MRI implementation is more performant.
So why doesn't it depend on the MRI version? bryanp/llhttp#12 mentions it's for better compatibility. Does that mean in the RPM packaging I'm doing I can simply swap out the dependency and package the more performant MRI version? I'm also this because packaging the FFI version is turning out to be complex.
Metadata
Metadata
Assignees
Labels
No labels