Async::HTTP::Faraday

Provides an adaptor for Faraday to perform async HTTP requests. If you are designing a new library, you should probably just use Async::HTTP::Client directly. However, for existing projects and libraries that use Faraday as an abstract interface, this can be a drop-in replacement to improve concurrency. It should be noted that the default Net::HTTP adapter works perfectly okay with Async, however it does not use persistent connections by default.

• Persistent connections by default.
• Supports HTTP/1 and HTTP/2 (and HTTP/3 in the future).

Usage

Please see the project documentation for more details.

• Getting Started - This guide explains how to use use Async::HTTP::Faraday as a drop-in replacement for improved concurrency.

Releases

Please see the project releases for all releases.

v0.22.1

• Fix memory leak in Async::HTTP::Faraday::PerThreadPersistentClients by ensuring that the close method is called on all clients when the adapter is closed.

v0.21.0

• Improved support for timeout and read_timeout.

v0.20.0

• Implement the new response streaming interface, which provides the initial response status code and headers before streaming the response body.
• An empty response now sets the response body to an empty string rather than nil as required by the Faraday specification.

v0.19.0

• Support in_parallel.

v0.18.0

• Support for config_block returning a middleware wrapper.

v0.17.0

• Introduced a per-thread Client cache.

Contributing

We welcome contributions to this project.

1. Fork the repository.
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Add some feature.').
4. Push to the branch (git push origin my-new-feature).
5. Create a new pull request.

Running Tests

To run the test suite:

$ bundle exec sus

Making Releases

To make a new release:

$ bundle exec bake gem:release:patch # or minor or major

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.