1.4.0 is a minor feature release that primarily improves pre-
1.1.0 version compatibility
and connection recovery features.
Changes between Langohr 1.3.0 and 1.4.0
Network Recovery Callbacks on Connections and Channels
They can be used to re-declare necessary entities using
1 2 3
Unlike OO clients that represent queues and exchanges as objects, Langohr cannot be more aggressive about redeclaring entities during connection recovery.
Changes between Langohr 1.2.0 and 1.3.0
The function creates a
QueueingConsumer instance and is very similar
langohr.consumers/create-default in purpose.
Sometimes combining a queueing consumer with
langohr.consumers/deliveries-seq is the best way to express a
Rename langoh.consumers/consumers-seq to langoh.consumers/deliveries-seq, make it public
langoh.consumers/deliveries-seq is a function that turns a
into a lazy sequence of deliveries.
Use :executor During Connection Recovery
Connection recovery after network failure will now respect the
Changes between Langohr 1.1.0 and 1.2.0
Langohr Again Uses RabbitMQ Java Client Interfaces
Langohr’s implementation of connection and channel now implements RabbitMQ Java client’s interfaces for connection and channel.
Langohr change log is available on GitHub.
Langohr is a ClojureWerkz Project
- Elastisch, a minimalistic well documented Clojure client for ElasticSearch
- Welle, a Riak client with batteries included
- 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.