DescriptionOne of the core principles of the design is that the server should only store the message payloads for a short time.
So need to have a thread (or something) running to periodically flush out older messages (I originally said 15 minutes, but 5 sounds better).
Activity
2018-05-12 16:21:40
The easiest (tm) way of doing it would be to add a new Flask routed path (say
But it means an extra step in the deployment.
I'm wondering if it might be better to spin up an additional thread which could periodically place the request (just as a cronjob would) to avoid the install procedure involving editing cronttab's (as if they're forgotten, or, deleted it could lead to leakage/compromise).
2018-05-14 08:54:52
So that thread would periodically (via urllib2) place a request to the API to trigger the purge. As this is potentially an expensive operation we should protect it with a passphrase to stop arbitrary users from triggering it and blocking the API.
At startup, the server app should generate a passphrase, which can then be passed into both the API request handler and the 'cron' thread.
2018-05-19 12:06:37
View Commit | View Changes
2018-05-19 12:24:37
View Commit | View Changes
2018-05-19 12:36:37
View Commit | View Changes
2018-05-19 12:38:36
View Commit | View Changes
2018-05-19 12:39:08
Marking this issue as complete (and we've now unblocked LOC-11 woohoo)
2018-05-19 12:39:15
2018-05-19 12:39:15
2018-05-19 12:39:18