diff options
| author | Matthias Radestock <matthias@rabbitmq.com> | 2013-03-21 17:28:32 +0000 |
|---|---|---|
| committer | Matthias Radestock <matthias@rabbitmq.com> | 2013-03-21 17:28:32 +0000 |
| commit | 0d6a7caf4ca1bb856d5054a107205e96cff655b4 (patch) | |
| tree | 6740be994ed49f54a963ac84d49d430b8858e1ab | |
| parent | 3dc0e6e04cb71ed1b8de0da64e0cd71909cb9d19 (diff) | |
| download | rabbitmq-server-git-0d6a7caf4ca1bb856d5054a107205e96cff655b4.tar.gz | |
fix typo
| -rw-r--r-- | src/rabbit_limiter.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rabbit_limiter.erl b/src/rabbit_limiter.erl index 602681e594..dfed5cb4ac 100644 --- a/src/rabbit_limiter.erl +++ b/src/rabbit_limiter.erl @@ -21,7 +21,7 @@ %% %% Each channel has an associated limiter process, created with %% start_link/1, which it passes to queues on consumer creation with -%% rabbit_amqqueue:basic_consume/8, and rabbit_amqqueue:basic_get/4. +%% rabbit_amqqueue:basic_consume/9, and rabbit_amqqueue:basic_get/4. %% The latter isn't strictly necessary, since basic.get is not %% subject to limiting, but it means that whenever a queue knows about %% a channel, it also knows about its limiter, which is less fiddly. |
