Permalink
Browse files

Remove more traces of the :immediate property

  • Loading branch information...
1 parent 04784e1 commit b077bccf966a0e443390d68f2dd1051ba361341f Michael Klishin committed Dec 27, 2012
Showing with 0 additions and 17 deletions.
  1. +0 −17 articles/exchanges.md
View
@@ -356,13 +356,6 @@ An example:
<dt>:persistent</dt>
<dd>When set to true, AMQP broker will persist message to disk.</dd>
- <dt>:immediate</dt>
- <dd>
- This flag tells the server how to react if the message cannot be routed to a queue consumer immediately. If this flag is set to true, the server will return
- an undeliverable message to the producer with a basic.return AMQP method. If this flag is set to false, the server will queue the message, but with no guarantee
- that it will ever be consumed.
- </dd>
-
<dt>:mandatory</dt>
<dd>
This flag tells the server how to react if the message cannot be routed to a queue. If this flag is set to true, the server will return an unroutable message
@@ -469,16 +462,6 @@ The following code example demonstrates a message that is published as mandatory
{% gist 98a17fe7b7a0619b3b36 %}
-### Publishing messages as immediate
-
-When publishing messages, it is possible to use the `:immediate` option to publish a message as "immediate". When an immediate message cannot be
-delivered to any consumer (meaning that one or more queues to which the message was routed have no active consumers), then the message is returned to the producer.
-
-<div class="alert alert-error">
-RabbitMQ versions starting with 2.9 drop support for the `:immediate` flag.
-</div>
-
-
### Returned messages
When a message is returned, the application that produced it can handle that message in different ways:

0 comments on commit b077bcc

Please sign in to comment.