Add maximum back-off parameter for "limit"?
The "limit" parameter causes an exponential back-off of messages, apparently with no upper limit on the interval between allowed messages. It would be nice if there could be an upper limit to this interval, so for example,
limit : 5
max_backoff : 100
would result in
1, 2, 3, 4, 5, 10, 15, 25, 45, 85, 185, 285, 385, ....
(By the way, I'm taking the 1st 10 numbers from the documentation. Wouldn't it actually be
1, 2, 3, 4, 5, 10, 20, 40, ....?)
Budget note: we couldn't pay for this on NOvA project. I assume MF support is already from non-project funds?
Schedule note: Please take due date with a grain of salt - not at all urgent.
#1 Updated by Christopher Green about 7 years ago
- Due date changed from 02/28/2013 to 09/30/2013
- Status changed from New to Accepted
- Assignee deleted (
- Target version set to 1.09.00
- Start date deleted (
- Estimated time set to 0.00 h
This should be implemented as part of the solution for issue #3571, and should not take any time over the estimate for that issue.