OceanCron: Refactor to be a separate program
Issue #281
new
There is little code in common between VidGrind in non-cron mode vs. cron mode.
It is proposed factoring out the cron mode code into a separate program, OceanCron (i.e., the name of the service), so it is no longer part of VidGrind. This would simplify the code and make each program more maintainable. Changes to VidGrind would be less likely to break OceanCron and vice versa.
Common code should first move to iotsvc.
Comments (1)
-
reporter
- Log in to comment
The main obstacle to refactoring OceanCron to become a separate program are the hard-coded broadcast functions that are called from the various crons.
If instead of calling a function, the crons invoked an RPC, OceanCron could be completely decoupled from VidGrind (and other services).
In other words, cron call actions would be replaced with rpc actions.