summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthias Radestock <matthias@rabbitmq.com>2013-02-20 17:54:00 +0000
committerMatthias Radestock <matthias@rabbitmq.com>2013-02-20 17:54:00 +0000
commitcf56799e48ed7dedbf0060f217b96d50c2868ddc (patch)
treef30289993cd3d50dad47cc9e7761a7e33d83b0ad
parent1a3bde0490e78fe41ff61f903a4c688b2ccf284d (diff)
downloadrabbitmq-server-cf56799e48ed7dedbf0060f217b96d50c2868ddc.tar.gz
cosmetic
-rw-r--r--src/rabbit_amqqueue_process.erl10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/rabbit_amqqueue_process.erl b/src/rabbit_amqqueue_process.erl
index de3e73ee..9fd85bd6 100644
--- a/src/rabbit_amqqueue_process.erl
+++ b/src/rabbit_amqqueue_process.erl
@@ -761,11 +761,11 @@ calculate_msg_expiry(#basic_message{content = Content}, TTL) ->
T -> now_micros() + T * 1000
end.
-%% Logically this function should invoke maybe_send_drained/1. However, that's
-%% expensive, and some frequent callers of drop_expired_msgs/1 (in particular
-%% deliver_or_enqueue/3) cannot possibly cause the queue to become empty, so
-%% instead we push the responsibility to the call sites. So be cautious when
-%% adding new ones.
+%% Logically this function should invoke maybe_send_drained/2.
+%% However, that is expensive. Since some frequent callers of
+%% drop_expired_msgs/1, in particular deliver_or_enqueue/3, cannot
+%% possibly cause the queue to become empty, we push the
+%% responsibility to the callers. So be cautious when adding new ones.
drop_expired_msgs(State = #q{backing_queue_state = BQS,
backing_queue = BQ }) ->
case BQ:is_empty(BQS) of