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
Why do the GUI and the Daemon duplicate the same functionality and responsibilites, like the scheduling code?
Wouldn't it be a better architecture to always have the Daemon handle scheduled/deferred Tasks and the GUI is just there for looking at the current state (like Snapshots, Statistics etc.) and i.e. to look at logs, and perhaps a timeline of the Daemon, or potentially even configuring the Daemon?
This would also eliminate the need for the GUI to be constantly running and instead bring it to a just "use when needed" role, which would be a better separation of concerns imho.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Why do the GUI and the Daemon duplicate the same functionality and responsibilites, like the scheduling code?
Wouldn't it be a better architecture to always have the Daemon handle scheduled/deferred Tasks and the GUI is just there for looking at the current state (like Snapshots, Statistics etc.) and i.e. to look at logs, and perhaps a timeline of the Daemon, or potentially even configuring the Daemon?
This would also eliminate the need for the GUI to be constantly running and instead bring it to a just "use when needed" role, which would be a better separation of concerns imho.
All reactions