Skip to content

Why is llhttp-ffi required instead of llhttp #797

@ekohl

Description

@ekohl

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions