You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first two do the same thing when a notification happens:
Join/connect to a server
Send a notification.
Disconnect
It would be neater if they could join in their constructor, and remain connected thereafter.
So the IRC notifier would join the channel and idle
The MQ notifier would connect to the queue.
And only at the notification stage would they actually notify. I'd suggest changing/extending the notifier class to have:
Setup()
Notify()
In the case of purppura the Setup() method would be a NOP, but for IRC/MQ they would join/connect there, and trigger notifications on demand via those persistent connections.
The text was updated successfully, but these errors were encountered:
Right now there are three notifiers:
The first two do the same thing when a notification happens:
It would be neater if they could join in their constructor, and remain connected thereafter.
And only at the notification stage would they actually notify. I'd suggest changing/extending the notifier class to have:
Setup()
Notify()
In the case of purppura the
Setup()
method would be a NOP, but for IRC/MQ they would join/connect there, and trigger notifications on demand via those persistent connections.The text was updated successfully, but these errors were encountered: