I’ve just released 0.1.0. It contains quite a few new features, the most noticeable being:
- Making sure we’re a well-behaved NIF and always return in less than 1 ms. Previously this was not guaranteed to be the case when the request body was very large.
- [Breaking change] Splitting the sync and async APIs for clarity. Everything in
erqwestis now synchronous and the async interface lives inerqwest_async. - Streaming support (of request and response bodies). Getting the API right was a bit tricky but I think it worked out well. I wanted to ensure that the sync API is always “safe”, ie. that it is impossible to end up in a state where a function call hangs indefinitely waiting for a message, or where you end up with stray messages in your inbox, even if you use the API incorrectly. I also wanted to ensure that the ergonomics of non-streaming use are not compromised.
- [Breaking change] As a result of the above the message format for the async API has changed.
- [Breaking change] The tokio runtime is now monitored by an erlang supervisor. This means you need to start the application (
:application.ensure_started(:erqwest)) before using it. - Optional cookies and gzip support. These are off by default since the extra dependencies increase the rust compile times. You set an env var at compile time to enable them (I’m not sure if there’s a better way to handle optional dependencies with rebar3, if you have ideas please let me know!).
See the readme for examples of how to use the new streaming API and grab the new version from hex where you can also find the docs 
