native curl > plenary job curl

[Conni2461]

Thats more of a tracking issue. I kinda wanna do it but want some opinions first.

@tami5 Curl is great but we have way too many layers:

• lua -> plenary job -> uv.spawn -> cli interface -> c -> profit

I was thinking maybe we could just rewrite it with native c bindings (ffi) which would give us something like this:

• lua -> (ffi) -> c -> mega profit

Currently i am thinking having a curl, curl_job and curl_native module. We try to load native curl and if that isn't available then we fallback to curl_job. curl is basically the public interface which will handle the fallback.

So if someone says i only wanna support curl_native he can also just call that.

We can also do some curl_extension stuff that is not supported with curl_job. Like providing stuff for the curl_multi interface. See here section The multi Interface

@tjdevries "Overkill" for plenary to do something like this?

[kkharji]

curl, curl_job and curl_native module.

Makes sense

[Conni2461]

And if ppl still think ours is not enough they can still use https://github.com/Lua-cURL/Lua-cURLv3 with luarocks/packer

[tjdevries]

@Conni2461 you're allowed to merge whatever you want here if you're having fun and it works. :)

Seems like a cool idea

[Conni2461]

Kinda unnecessary 😆