diff options
| author | Ask Solem <askh@opera.com> | 2010-08-04 13:46:10 +0200 |
|---|---|---|
| committer | Ask Solem <askh@opera.com> | 2010-08-04 13:53:43 +0200 |
| commit | fd0296af7bd1e095e4d4b709c9e8d8c16fbacbdd (patch) | |
| tree | 61a1c5e717e9a53f499f29b8937a4d0c95a680a9 /README.rst | |
| parent | df3d885cd723bc785c045bb6b2028f9800829f0f (diff) | |
| download | kombu-fd0296af7bd1e095e4d4b709c9e8d8c16fbacbdd.tar.gz | |
All occurences of the term Backend has been replaced with Transport.
kombu.backends -> kombu.transport
BrokerConnection(backend_cls="pika") -> BrokerConnection(transport="pika")
kombu.backends.base.BaseBackend -> kombu.transport.base.Transport
kombu.backends.pyredis.RedisBackend -> kombu.transport.pyredis.Transport
etc, etc.
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -72,10 +72,10 @@ The aim of ``kombu`` is to make messaging in Python as easy as possible by providing a high-level interface for producing and consuming messages. At the same time it is a goal to re-use what is already available as much as possible. -`kombu` has pluggable messaging back-ends, so it is possible to support +`kombu` has pluggable messaging transports, so it is possible to support several messaging systems. Currently, there is support for `AMQP`_ (`py-amqplib`_, `pika`_), `STOMP`_ (`stompy`_). There's also an -in-memory backend for testing purposes, using the `Python queue module`_. +in-memory transport for testing purposes, using the `Python queue module`_. Several AMQP message broker implementations exists, including `RabbitMQ`_, `Apache ActiveMQ`_. You'll need to have one of these installed, |