Skip to content

Multiple message queues for a bot #1369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alistvt opened this issue Mar 22, 2019 · 5 comments
Closed

Multiple message queues for a bot #1369

alistvt opened this issue Mar 22, 2019 · 5 comments

Comments

@alistvt
Copy link

alistvt commented Mar 22, 2019

I just read this source of the decorator @messagequeue
and I thought what if a bot needs multiple message queues?
because the limits in telegram are different for each type of requests.
for example the limit for editing message texts is too low!

what do you suggest to do?

Thanks.

@alistvt alistvt changed the title message queue Multiple message queues for a bot Mar 22, 2019
@jsmnbom
Copy link
Member

jsmnbom commented Mar 27, 2019

We currently don't have anything implemented that can do that kinda thing. We'd probably be open to suggestions/PRs with how such a thing should be done tho! :D

@Poolitzer
Copy link
Member

On one hand, it might even be interesting to do this behind the scenes. So we add each request in a queue and try to be smart when we do what so we dont hit limits.

On the other hand, there is nothing we can do if a user sends 60 requests at once, and they should limit such a bulk request by themself in the code actually.

@Maga007

This comment has been minimized.

@Bibo-Joshi

This comment has been minimized.

@Bibo-Joshi
Copy link
Member

As we won't tackle this issue individually but in the context of #2139, I will close this. #2139 links here, so it won't be forgotten :)

@github-actions github-actions bot locked and limited conversation to collaborators Jan 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants