start daemon to for one account and one conversation
To improve CPU and memory usage for notifications, we should have the option to start a daemon for just one account and one conversation.
There are two possible workflows:
-
In the first workflow, for every notification, the manager is initialized and started, the account and conversation are loaded, and then the manager is stopped. Currently, the destruction of the manager is not supported.
-
In the second workflow, the manager is initialized and started only once. Then, for every notification, the account is loaded (if not already loaded), the conversation is loaded, the account is set as active, and then set as not active once the notification has been processed.