Implement update grouping to make less API requests #41
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Miroslavsckaya/tg_rss_bot#41
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now we're making at 1+N requests to Telegram API each time we're sending updates to the user.
We can operate with Telegram API more efficiently by implementing message grouping.
But we need to remember about message length limit and modify current solution (#40) to a bit more sophisticated one.