Skip to content

Commit

Permalink
Adding MessageQueue support to avoid hitting flood limits.
Browse files Browse the repository at this point in the history
  • Loading branch information
alistvt committed Dec 28, 2018
1 parent ce10c5a commit 903d4f7
Show file tree
Hide file tree
Showing 3 changed files with 267 additions and 218 deletions.
9 changes: 9 additions & 0 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,14 @@ And set your bots::
#delivery, 1-100. Defaults to 40. Use lower values to limit the
#load on your bot's server, and higher values to increase your
#bot's throughput.
# 'MESSAGEQUEUE_ENABLED':(Optinal[bool]), # Make this True if you want to use messagequeue

# 'MESSAGEQUEUE_ALL_BURST_LIMIT':(Optional[int]), # If not provided 29 is the default value

# 'MESSAGEQUEUE_ALL_TIME_LIMIT_MS':(Optional[int]), # If not provided 1024 is the default value

# 'MESSAGEQUEUE_REQUEST_CON_POOL_SIZE':(Optional[int]), # If not provided 8 is the default value

#'POLL_INTERVAL' : (Optional[float]), # Time to wait between polling updates from Telegram in
#seconds. Default is 0.0
Expand Down Expand Up @@ -189,6 +197,7 @@ Features
* Polling mode by management command (an easy to way to run bot in local machine, not recommended in production!)

``(myenv) $ python manage.py botpolling --username=<username_bot>``
* Supporting messagequeues

Contributing
------------
Expand Down
Loading

0 comments on commit 903d4f7

Please sign in to comment.