Since we have a lot of issues and requests for making utilities to get, handle and process telegram updates, we need to create separate subsystem for it. It must be splitted by specific subsystem. cause some projects doesn't need get updates at all.
Solution:
The idea is to make a separate subpackage that wraps around the telegram.Client itself, very similar to the existing deeplinks package. Perhaps we will be able to make a manager of such updates so as not to load the main components (telegram.Client andmtproto.Client), since not in all cases users need to receive updates.
Possible alternatives:
Leave this problem to end users, but i'm not sure that it's a good solution.
Additional context
Linked issues:
72 updates channel stops exactly after 1 minute after calling cleint.UpdatesGetState
Problem description:
Since we have a lot of issues and requests for making utilities to get, handle and process telegram updates, we need to create separate subsystem for it. It must be splitted by specific subsystem. cause some projects doesn't need get updates at all.
Solution:
The idea is to make a separate subpackage that wraps around the
telegram.Client
itself, very similar to the existing deeplinks package. Perhaps we will be able to make a manager of such updates so as not to load the main components (telegram.Client
andmtproto.Client
), since not in all cases users need to receive updates.Possible alternatives:
Leave this problem to end users, but i'm not sure that it's a good solution.
Additional context
Linked issues:
72 updates channel stops exactly after 1 minute after calling
cleint.UpdatesGetState