mirror of
https://github.com/aiogram/aiogram.git
synced 2025-12-12 10:11:52 +00:00
36 lines
1,021 B
ReStructuredText
36 lines
1,021 B
ReStructuredText
===============
|
|
Handling events
|
|
===============
|
|
|
|
*aiogram* includes Dispatcher mechanism.
|
|
Dispatcher is needed for handling incoming updates from Telegram.
|
|
|
|
With dispatcher you can do:
|
|
|
|
- Handle incoming updates;
|
|
- Filter incoming events before it will be processed by specific handler;
|
|
- Modify event and related data in middlewares;
|
|
- Separate bot functionality between different handlers, modules and packages
|
|
|
|
Dispatcher is also separated into two entities - Router and Dispatcher.
|
|
Dispatcher is subclass of router and should be always is root router.
|
|
|
|
Telegram supports two ways of receiving updates:
|
|
|
|
- :ref:`Webhook <webhook>` - you should configure your web server to receive updates from Telegram;
|
|
- :ref:`Long polling <long-polling>` - you should request updates from Telegram.
|
|
|
|
So, you can use both of them with *aiogram*.
|
|
|
|
.. toctree::
|
|
|
|
router
|
|
dispatcher
|
|
class_based_handlers/index
|
|
filters/index
|
|
middlewares
|
|
finite_state_machine/index
|
|
flags
|
|
errors
|
|
long_polling
|
|
webhook
|