TL;DR
Langohr is a small Clojure RabbitMQ client.
2.9.0
is a minor feature release.
Changes between Langohr 2.8.x and 2.9.0
Configurable Default and Per-Operation Options in HTTP API Client
Most HTTP API client functions now have an additional optional arguments,
which is a map of options passed to clj-http
functions. This lets you fine
tune certain HTTP requests as needed.
In addition, langohr.http/connect!
now accepts one more argument which serves
as default HTTP client options merged with the options provided per langohr.http
function call:
1 2 3 4 5 6 7 8 9 10 11 12 |
|
Thread Factory Customization
It is now possible to customize a java.util.concurrent.ThreadFactory
used by Langohr connections. The factory will be used to instantiate
all threads created by the client under the hood.
The primary use case for this is running on Google App Engine which prohibits direct thread instantiation and requires apps to use thread manager (or thread factory) from GAE SDK instead.
To provide a custom thread factory, pass it as :thread-factory
to
langohr.core/connect
. To reify a thread factory with a Clojure function,
use langohr.core/thread-factory-from
:
1 2 3 4 5 6 |
|
com.rabbitmq.client.TopologyRecoveryException is Used
Langohr now uses com.rabbitmq.client.TopologyRecoveryException instead of reinventing its own exception to indicate topology recovery failure.
RabbitMQ Java Client Compatibility
A few RabbitMQ Java client interface compatibility issues are resolved.
Change Log
Langohr change log is available on GitHub.
Langohr is a ClojureWerkz Project
Langohr is part of the group of libraries known as ClojureWerkz, together with
- Elastisch, a minimalistic well documented Clojure client for ElasticSearch
- Cassaforte, a Clojure Cassandra client built around CQL 3.0
- Monger, a Clojure MongoDB client for a more civilized age
- Neocons, a client for the Neo4J REST API
- Quartzite, a powerful scheduling library
and several others. If you like Langohr, you may also like our other projects.
Let us know what you think on Twitter or on the Clojure mailing list.
About The Author
Michael on behalf of the ClojureWerkz Team