diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2011-04-01 11:55:08 +0100 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2011-04-01 11:55:08 +0100 |
| commit | d372155b0821bf65c5e82eecd6f84f5bce216ac8 (patch) | |
| tree | 6495c5113e3bc3feee60160e5f76a998a9c473c1 /src/rabbit_exchange_type.erl | |
| parent | ff083aa2ddb84a35c106465d27035f5df78c3166 (diff) | |
| parent | 9d173dc01bb2f1c796fdb29fc69e429ce1f783bd (diff) | |
| download | rabbitmq-server-d372155b0821bf65c5e82eecd6f84f5bce216ac8.tar.gz | |
Merge bug 24009 into bug 23939.
Diffstat (limited to 'src/rabbit_exchange_type.erl')
| -rw-r--r-- | src/rabbit_exchange_type.erl | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/src/rabbit_exchange_type.erl b/src/rabbit_exchange_type.erl index ad08eb86..0468683e 100644 --- a/src/rabbit_exchange_type.erl +++ b/src/rabbit_exchange_type.erl @@ -21,6 +21,13 @@ behaviour_info(callbacks) -> [ {description, 0}, + + %% Should Rabbit ensure that all binding events that are + %% delivered to an individual exchange can be serialised? (they + %% might still be delivered out of order, but there'll be a + %% serial number). + {serialise_events, 0}, + {route, 2}, %% called BEFORE declaration, to check args etc; may exit with #amqp_error{} |