Todo Items of Week Beginning Friday Jan. 23th

[RobertLRead]

1. Subscriber file and duplicate to called "Krake_Simulator.py"
2. The Krake_Simulator is simpler than the current subscriber (It only has 1 alarm, and cannot remember alarms.) (See line 16).
3. The AdamServer needs to know what alarm was last sent to the Krake_Simulator, so it can implement Serial
4. The Krake_Simulaor no longer lets you list alarms --- It writes over it on the screen, showing the last alarm.
5. Transfer most of the subscribe.py should be moved into the server.
6. The Krake_Simulator does not have a POLICY.
7. The AdamServer keeps ALL unacknowledged alarms, and sends the oldest, highest priority alarm to the Krake_Simulator.
8. Create SEVERITY_PAUSE as a policy. SEVERITY_PAUSE defines a 20-second pause, and won't rewrite an alarm until the user has had it for 20 seconds. (20 sould be configurable.)
9. Implement a "Strategy" Gang-of-four Design Pattern. POLICY0, SEVERITY, SEVERITY_PAUSE are all different algoithms that are part of a "Strategy".
10. Move constant at line 192 defining which broker/port to use into configuration file.
11. Make Server output a log file of all actions in log file with timestamp (via append).
12. RECEIVE AND ALARM
13. SEND AN ALARM
14. RECEIVE ACKNOWLEDGMENT
15. (Look for python equivalent of "Log4J" library
16. Consider creating "game" via simulator that creates N random alarms like the game you programmed before, and uses log file to assign "harm score". Possibly put a "name" in each alarm so that they can be identified.
17. Start using the Krake-defined alarm protocol: Alarm is not JSON. "a"[0-5][.]*" -- "a", a digit, and 80 characters and then EOLN characters.