/
The curl footprint is an elephant

The curl footprint is an elephant

We expose a lot of functionality with curl - how are we going to replace it? It’s like the problem of how to eat an elephant.

We can apply 80-20 rule and start with HTTP.

Related content

Think of curl as a code dump
Think of curl as a code dump
More like this
Make a better user experience
Make a better user experience
More like this
Advantages of not hard coding HTTP clients with Curl
Advantages of not hard coding HTTP clients with Curl
More like this
How could we better help customers who get upset where our protocol implementations don't meet their needs?
How could we better help customers who get upset where our protocol implementations don't meet their needs?
More like this
Not hard coding Curl into IguanaX means less risks from bugs, incompatible changes and other security flaws
Not hard coding Curl into IguanaX means less risks from bugs, incompatible changes and other security flaws
More like this
How could we help our customers migrate to our own implementation of HTTP etc. instead of using Curl?
How could we help our customers migrate to our own implementation of HTTP etc. instead of using Curl?
Read with this